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
  • atlas rpc
  • atlas consensus rpc
  1. MAPO Stack
  2. SDK/API
  3. Atlas RPC

json-rpc

PreviousAtlas RPCNextatlas json rpc

Last updated 1 year ago

In order for a software application to interact with the MAPO-Relay-Chain blockchain (by reading blockchain data or sending transactions to the network), it must connect to MAPO-Relay-Chain nodes or its provided .

The following MAPO-Relay-Chain is collectively referred to as MAPO.

JSON-RPC (JavaScript Object Notation Remote Procedure Call) is a lightweight remote procedure call (RPC) protocol that utilizes JSON as the data exchange format. JSON-RPC enables cross-network communication between clients and servers for invoking remote services or methods, similar to traditional RPC protocols, but with data transmission in JSON format.

The key features of JSON-RPC include:

  • Lightweight: JSON-RPC uses JSON, a lightweight data exchange format that is easy to parse and generate.

  • Language-agnostic: JSON-RPC is not tied to a specific programming language or platform, enabling communication between different programming languages.

  • Transport Protocol Flexibility: JSON-RPC can operate over various transport protocols, with the most common being HTTP for communication but also capable of using other protocols such as WebSocket.

  • Simplicity: The JSON-RPC protocol specification is relatively simple and straightforward to implement.

JSON-RPC requests typically consist of the following parts:

  • Method Name (Method): The name of the remote method or function to be invoked.

  • Parameters (Params): The parameters passed to the remote method, often an array or an object.

  • ID (Identifier): A unique identifier used to associate requests and match responses, usually an integer or a string.

  • JSON-RPC responses contain the following components:

  • Result (Result): The result of the remote method's execution, often an array or an object.

  • Error (Error): If an error occurs, this part contains an object with error information.

  • ID (Identifier): Corresponding to the ID in the request, used to match responses with requests.

JSON-RPC is widely used in building distributed systems, web services, blockchain node communication, and other scenarios due to its lightweight and language-agnostic nature, allowing applications in different platforms and languages to communicate with each other. Some well-known blockchain platforms, such as Ethereum, also use JSON-RPC as a means of communication with client applications.

atlas rpc

atlas consensus rpc

MAPO provides a JSON-RPC API that is compatible with Ethereum's API. For specific details about this API, please refer

MAPO also provides a set of consensus-related APIs. For specific details about these APIs, please refer

public network
this
this