KyberSwap Docs
  • Introduction to KyberSwap
  • Getting Started
    • Quickstart
      • FAQ
    • Supported Exchanges And Networks
    • Foundational Topics
      • Decentralized Finance
        • Tokens
        • Stablecoins
        • DEX/DeFi Aggregator
        • Slippage
        • Price Impact
        • Zap
        • Maximal Extractable Value (MEV)
      • Decentralized Technologies
        • Wallets
        • Dapps
        • RPC
        • Oracles
        • On-Chain vs Off-Chain Data
      • Other Valuable Resources
  • KyberSwap Solutions
    • KyberSwap Interface
      • User Guides
        • Connect Your Wallet
        • Switching Networks
        • Instantly Swap At Superior Rates
        • Swap At Your Preferred Rates
        • Cross-chain Swap
        • Add Your Favourite Tokens
        • Get Crypto With Fiat
        • Bridge Your Assets Across Multiple Chains
      • Profiles
        • Profile Creation
        • Profile Customization
        • Sync Profile Across Devices
      • Notifications
        • Notification Center
    • KyberSwap Aggregator
      • Concepts
        • Dynamic Trade Routing
      • User Guides
        • Instantly Swap At Superior Rates
      • Developer Guides
        • Execute A Swap With The Aggregator API
        • Upgrading To APIv1
      • Aggregator API Specification
        • EVM Swaps
        • Permit
      • Contracts
        • Aggregator Contract Addresses
      • DEX IDs
      • Subgraphs
      • FAQ
    • KyberSwap Zap as a Service
      • KyberSwap Zap as a Service (ZaaS) API
        • ZaaS HTTP API
        • ZaaS GRPC API
      • KyberSwap Zap Liquidity Widget
      • Zap Fee Model
      • Zap's Supported Chains/Dexes
      • Zap's Deployed Contract Addresses
      • Zap's DEX IDs
    • KyberSwap Widget
      • Developer Guides
        • Integrating The KyberSwap Widget
        • Customizing The KyberSwap Widget
      • iFrame Alternative
      • Widget/iFrame Fee
    • KyberSwap Liquidity Widget
      • Integrating The KyberSwap Liquidity Widget
    • Limit Order
      • Concepts
        • Off-Chain Relay, On-Chain Settlement
        • Gasless Cancellation
      • User Guides
        • Swap At Your Preferred Rates
        • Update Limit Orders
        • Cancel Limit Orders
      • Developer Guides
        • Create Limit Order
        • Gasless Cancel
        • Hard Cancel
        • Fill Limit Order
      • Contracts
        • Limit Order Contract Addresses
      • Limit Order API Specification
        • General APIs
        • Maker APIs
        • Taker APIs
      • FAQ
    • KyberSwap OnChain Price Service
    • Fee Schedule
  • Governance
    • KyberDAO
      • User Guides
        • Participating in KyberDAO
        • Staking
        • Voting
        • Stake KNC And Enjoy Gas Savings
      • Fees to KyberDAO
      • KyberDAO Operator MultiSig
      • Contracts
        • KyberDAO Contract Repo
        • KyberDAO Contract Addresses
      • FAQ - Others
    • KNC Token
      • KNC Tokenomics & Utility
      • Gas Refund Program
      • KNC Contract Addresses
  • Security
    • Audits
  • Reference
    • Legacy
      • KyberSwap Classic
        • Concepts
          • Programmable Pricing Curves
          • Dynamic Auto-Adjusting Fees
          • Virtual Balances
          • Protocol Fees
        • Contracts
          • Classic Contract Repo
          • Classic Contract Addresses
          • Classic Contract Farming Addresses
      • KyberSwap Elastic
        • Concepts
          • Concentrated Liquidity
          • Reinvestment Curve
          • Tick-Range Mechanism
          • Pool Process Flows
          • Anti-Sniping Mechanism
          • Tick-Based Farming
          • Elastic Zap
          • TWAP Oracle
          • Elastic APR Calculations
        • Contracts
          • Elastic Contract Repo
          • Elastic Contract Addresses
          • Elastic Farming Contract Addresses
          • Elastic Zap Contract Addresses
          • Elastic Core Contracts
          • Elastic Core Libraries
          • Elastic Periphery Core Contracts
          • Elastic Peripheral Library Contracts
          • Elastic Peripheral Base Contracts
        • Subgraphs
      • Whitepapers
      • Audits
      • KyberAI
        • KyberScore
        • Concepts
        • On-Chain Indicators
          • Number Of Trades
          • Trading Volume
          • Netflow To Whale Wallets
          • Netflow To CEX
          • Number Of Transfers
          • Volume Of Transfers
          • Number Of Holders
          • Top Holders
        • Technical Indicators
          • Live Charts
          • Support & Resistance Levels
          • Live Trades
          • Funding Rate On CEX
          • Liquidations On CEX
        • Liquidity Analysis
      • Elastic Legacy
        • Elastic Legacy Contract Repo
        • Elastic Legacy Contract Addresses
        • Elastic Legacy Farming Contract Addresses
        • Remove Elastic Legacy Liquidity
      • Protocol
        • Overview
        • Smart Contract Architecture
        • Trust and Security Model
      • Integrations
        • Getting Started
        • Use Cases
        • Integration Types
        • Smart Contracts
        • Ethers JS
        • RESTful API
        • Slippage Rate Protection
        • Price Feed Security
        • Contract Events
        • Platform Fees
      • Reserves
        • Getting Started
          • Overview
          • Why Develop On Kyber
          • Create New Reserve
          • Existing Reserves
          • Customising Existing Reserves
        • Development Guides
          • Fed Price Reserve
          • Automated Price Reserve
          • Reserves with Ganache
          • Orderbook Reserve
        • Operations
          • Listing Policies
          • Reserve IDs
          • Reserve Rebates
          • Sanity Rates
      • Addresses
        • Introduction
        • Mainnet
        • Kovan
        • Rinkeby
        • Ropsten
      • API/ABI
        • Introduction
        • RESTful API
          • RESTful API Overview
          • RESTful API
        • Core Smart Contracts
          • IKyberNetworkProxy
          • KyberNetworkProxy
          • IKyberNetwork
          • ISimpleKyberProxy
          • IKyberMatchingEngine
          • KyberMatchingEngine
          • IKyberHint
          • KyberHintHandler
          • IKyberHintHandler
          • IKyberFeeHandler
          • IKyberStaking
          • KyberStaking
          • IKyberDao
          • KyberDao
          • IKyberStorage
          • KyberStorage
          • IKyberHistory
          • KyberHistory
          • IKyberReserve
          • KyberReserve
          • ConversionRates
          • LiquidityConversionRates
          • EpochUtils
          • IEpochUtils
          • KyberFeeHandler
        • Contract ABIs
          • ABIs
        • Code Snippets
          • Token Quantity Conversion
        • Misc Contracts
          • KyberNetwork
          • ConversionRatesInterface
          • PermissionGroups
          • SanityRates
          • Withdrawable
          • OrderbookReserveInterface
          • OrderbookReserveLister
    • KyberSwap Operator MultiSig
    • Permitable Tokens
    • Third-Party Integrations
    • KyberSwap Analytics
    • KyberSwap App
    • GitHub
    • KyberSwap Analytics
    • KyberSwap Blog
    • Kyber Network Press Kit
  • Socials
    • X
    • Discord
    • Telegram
    • LinkedIn
    • Reddit
    • Instagram
    • Tik Tok
  • Support
    • KyberSwap Help Center
    • Complaints Handling Process
Powered by GitBook
On this page
  • Overview
  • RPC: Protocol, Nodes, Endpoints
  • Selecting a RPC

Was this helpful?

  1. Getting Started
  2. Foundational Topics
  3. Decentralized Technologies

RPC

Connecting Dapps To The Blockchain

PreviousDappsNextOracles

Last updated 1 year ago

Was this helpful?

Overview

In the Web3 space, a RPC is a shorthand which generally refers to how a gets data from a blockchain. While data is transparently stored on the blockchain, querying and sorting the publicly available data is highly resource intensive. Moreover, given the immediacy of on-chain data, performance requirements usually dictate that transaction logic be computed on a full node which holds the full transaction history of the blockchain. As dapps are meant to be lightweight pieces of code that can conveniently run on a web-page or mobile browser, this approach is infeasible and that is where RPCs come in handy.

To achieve a better user experience for Web3 users, RPCs enable the following to be functionally separated:

  • Dapps handle user interactions whereby users can view blockchain data and update such data by providing a signed instruction. Dapps do not need to hold onto all the blockchain data nor have the necessary computing resources to execute the transaction. As such, users can easily access dapps from any device with minimal concerns about hardware or network requirements.

  • RPC nodes essentially run blockchain software and are therefore required to hold onto the full set of blockchain data and be able to reliably execute transactions. This requires significantly more computing resources and specialized hardware. By exposing an endpoint, RPC nodes enable dapps to query on-chain data as well as send signed instructions to be executed by the RPC node.

In short, RPCs allow dapps to focus on user interactions while leaving the complexity of translating and executing such user data to a node. Note that for simplicity, the above does not differentiate between the different types of nodes (i.e. light nodes, full nodes, etc.).

RPC: Protocol, Nodes, Endpoints

From a technical standpoint, a RPC actually refers to a Remote Procedure Call protocol but this distinction is usually overlooked for end user simplicity. For the purposes of accuracy, the differences are highlighted below:

  • Remote Procedure Call protocol is a standard interface which allows for a client (i.e. dapp) to remotely request for a server's (i.e. nodes) resources without requiring details on the server's location or network.

  • Remote Procedure Call nodes are the servers which receive the requests from the client (i.e. dapp) and compute the instructions by runnning the blockchain software.

  • Remote Procedure Call endpoints are the addresses which allows a client (i.e. dapp) to interface directly with the server (i.e. node)

In the large majority of cases, the term RPC is usually used to refer to the RPC endpoint which a user will interact with. Underlying this endpoint will of course be a RPC node which has been abstracted away.

Selecting a RPC

As each chain requires nodes to run a different set of blockchain software, users will have to change their connected RPC endpoint when switching between chains. You can refer to our on how to achieve this.

MEV Protection

KyberSwap allows users to select RPCs which protect the user's transactions against MEV strategies by routing the transaction into a private mempool. Please refer to MEV protection for more details.

In addition to switching between chains, there is also an element of trust when a user selects a specific RPC on a chain. This is because the execution of dapp logic ultimately depends on the RPC node reliably and objectively processing the signed instructions. A RPC which is consistently offline or slower to respond would result in a degraded user experience. Moreover, RPC nodes can even take advantage of the transaction data to execute thereby profiting at the expense of the user. As such, users will have to select RPCs based on a combination of factors.

dapp
Switching Networks guide
MEV strategies