MAPO Developer Docs
  • MAPO Developer Docs
  • Base
    • MAPO Introduction
    • MAPO token
    • Omnichain DAPP
    • Differences Between Omnichain Applications and Single or Multi-Chain Applications
    • Differences Between Third-Party Trusted Cross-Chain and Peer-to-Peer Cross-Chain Solutions
    • BTC layer2
      • brc-201
    • Oracle
      • Supra: Decentralized Oracle on MAP Protocol
    • Account
    • Transactions
    • block
    • MPT tree
    • RLP
    • Gas fee
    • Cross Chain Message
    • light client
      • MAPO light client
    • MOS
      • MOS interface and functions
      • deploy MOS
      • Messenger
    • map-relay-chain(atlas)
      • atlas architecture
        • atlas architecture
        • atlas genesis
          • genesis config
          • genesis contract
            • ABI
              • Accounts
              • Election
              • EpochRewards
              • LockedGold
              • Validators
            • address
            • deploy
        • precompile-contract
        • protocol
          • Proof of Stake
          • consensus
          • election
          • rewards
          • governance
      • deploy atlas
        • run atlas
        • run atlas(archive)
        • run atlas(bootnodes)
        • run atlas(validator)
        • run atlas(RPC)
      • Marker tool
        • Genesis
        • Validator
        • Vote
        • Common
      • make private network(atlas)
      • public service
        • public network
      • example
        • how-to-vote
        • how-to-withdraw
        • how-to-become-a-new-validator
        • how-to-become-a-new-validator(advanced)
    • Compass(maintainer,messenger)
      • Compass - arch and model
      • Compass - config
      • Compass - deploy
      • Compass secondary development - define your own routing service based on compass
  • MAPO Stack
    • stack
      • Connected Chains and Corresponding Addresses
    • Compatible-EVM
      • Smart Contracts Language
      • Smart Contracts Anatomy
      • Smart Contracts Libraries
      • Smart Contracts Compile
      • Smart Contracts Testing
      • Smart Contracts Deploy
      • Smart Contracts Composability
      • Smart Contracts Security
      • Formal-Verification
      • Frameworks
      • dev-network
    • MAPO Implement Cross-chain Interoperability
      • integration of MAP with EVM-Compatible Chains
        • light client verify
        • light client update state
        • MOS
      • integration of MAP with TON Network
      • integration of MAP with Non-EVM-Compatible Chains
        • light client verify
        • light client update state
        • MOS
    • How to develop cross-chain applications
    • light client address
    • SDK/API
      • MOS interface
      • Light client interface
      • Atlas RPC
        • json-rpc
          • atlas json rpc
          • atlas consensus rpc
        • javaScript sdk
        • go-sdk
      • Backend API
        • SCAN API
  • Zero-Knowledge Proof
    • zk proof
Powered by GitBook
On this page
  • What is an RPC node
  • How RPC nodes work
  • Running an RPC node
  1. Base
  2. map-relay-chain(atlas)
  3. deploy atlas

run atlas(RPC)

What is an RPC node

RPC (Remote Procedure Call) is a protocol for requesting services from a remote computer over a network without needing knowledge of the underlying network technology. RPC assumes the existence of certain protocols, such as TCP/UDP, to carry the information between communicating programs. In the OSI network model, RPC spans the transport layer and the application layer, making it easier to develop applications, including network distributed programs.

In blockchain technology, an RPC node plays a crucial role in communication. It serves as a specialized server that can connect decentralized applications (DApps) and the blockchain network. RPC nodes enable these applications to interact with the blockchain, facilitating tasks such as transaction verification and data retrieval.

How RPC nodes work

Understanding the operation of an RPC node requires knowledge of the client-server model that supports its functionality. In this architecture, the RPC node acts as a server, receiving requests from client applications. These requests range from querying blockchain data to executing transactions. Once the server receives a request, it processes the necessary operations and returns the results to the client application, completing the communication cycle.

The mechanism of this interaction is governed by a set of rules, often encapsulated in a protocol. In the case of blockchain, the JSON-RPC protocol is an industry standard. This lightweight protocol uses JSON encoding to facilitate data exchange between client and server. It defines a set of methods that client applications can invoke, whether to initiate transactions or retrieve specific blockchain data. The JSON-RPC protocol ensures standardized and efficient interaction between applications and the blockchain network.

The operation of an RPC node is straightforward. The client application sends a request to the RPC node, specifying the functionality it wants to perform. This request is formatted according to the JSON-RPC protocol. The server processes the request, executes the function, and returns the result (also in JSON format). This request and response cycle allows decentralized applications to seamlessly operate, access blockchain data, and execute transactions.

RPC nodes operate on the client-server model, facilitating communication between decentralized applications and the blockchain network. The JSON-RPC protocol serves as the standard for these interactions, ensuring unified and efficient data exchange.

Running an RPC node

atlas --datadir ./node --syncmode "full" --http --http.addr "127.0.0.1" --http.port 7445 
Previousrun atlas(validator)NextMarker tool

Last updated 1 year ago