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
  • Ethereum
  • BNB Smart Chain
  • Polygon Mainnet
  • NEAR
  • Arbitrum One
  • Klaytn
  • Conflux
  • Tron
  • PlatON Mainnet
  • OP Mainnet
  • Base
  • Linea
  • zkSync
  • Merlin
  • Blast
  • Scroll
  • AILayer
  • Mantle
  • Ton Testnet
  • Solana
  • How to integrate MAP Protocol with EVM-Compatible Chains
  • How to integrate MAP Protocol with Ton Network
  • How to build a dApp with MAP Protocol
  1. MAPO Stack
  2. stack

Connected Chains and Corresponding Addresses

PreviousstackNextCompatible-EVM

Last updated 6 months ago

Below is MAP Protocol's latest chain connectivity progress and the corresponding contract addresses.

Ethereum

  • Light-client on MAPO Source Code: Address:

  • Light-client on Chain Source Code: Address:

  • MOS Source Code: Address:

  • Chain ID: 1

  • Status:Completed MAP Protocol <-> Ethereum

BNB Smart Chain

  • Light-client on MAPO Source Code: Address:

  • Light-client on Chain Source Code: Address:

  • MOS Source Code: Address:

  • Chain ID: 56

  • Status: Completed MAP Protocol <-> BNB Smart Chain

Polygon Mainnet

  • Light-client on MAPO Source Code: Address:

  • Light-client on Chain Source Code: Address:

  • MOS Source Code: Address:

  • Chain ID: 137

  • Status: Completed MAP Protocol <-> Polygon Mainnet

NEAR

  • Chain ID: 5566818579631833088

  • Status: Completed MAP Protocol <-> NEAR

Arbitrum One

  • Light-client on MAPO Source Code: N/A Address:N/A

  • Chain ID: 42161

  • Status: Completed MAP Protocol --> Arbitrum One

Klaytn

  • Chain ID: 8721

  • Status: Completed MAP Protocol <-> Klaytn

Conflux

  • Chain ID:1030

  • Status: Completed MAP Protocol <-> Conflux

Tron

  • Chain ID: 728126428

  • Status: MAP Protocol <--> Tron

PlatON Mainnet

  • Chain ID: 210425

  • Status: Coming soon

OP Mainnet

  • Chain ID: 10

  • Status: MAP Protocol --> OP Mainnet

Base

  • Chain ID: 8453

  • Status: MAP Protocol <--> Base

Linea

  • MOS: 0xfeB2b97e4Efce787c08086dC16Ab69E063911380

  • Chain ID: 59144

  • Status: MAP Protocol <--> Linea

zkSync

  • Chain ID: 324

  • Status: MAP Protocol <--> zkSync

Merlin

  • Chain ID: 4200

  • Status: MAP Protocol <--> Merlin

Blast

  • Chain ID: 81457

  • Status: MAP Protocol <--> Blast

Scroll

  • Chain ID: 534352

  • Status: MAP Protocol <--> Scroll

AILayer

  • Chain ID: 2649

  • Status: MAP Protocol <--> AINN

Mantle

  • Chain ID: 5000

  • Status: MAP Protocol <--> Mantle

Ton Testnet

  • Chain ID: 1360104473493506

  • Status: Completed MAP Protocol <-> Ton

Solana

  • Planning

How to integrate MAP Protocol with EVM-Compatible Chains

How to integrate MAP Protocol with Ton Network

How to build a dApp with MAP Protocol

Light-client on MAPO Source Code: Address:

Light-client on Chain Source Code: Address:

MOS Source Code: Address:

Light-client on Chain Source Code: Address:

MOS Source Code: Address:

Light-client on MAPO Source Code: Address:

Light-client on Chain Source Code: Address:

MOS Source Code: Address:

Light-client on MAPO Source Code: Address:

Light-client on Chain Source Code: Address:

MOS Source Code: Address:

OracleNode on MAPO Address:

OracleNode on Chain Address:

Light-client on MAPO Source Code: Address:Coming soon

Light-client on Chain Source Code: Address: Coming soon

MOS Source Code: Address: Coming soon

OracleNode on MAPO Address:

Light-client on Chain Source Code: Address:

MOS Source Code: Address:

OracleNode on MAPO Address:

Light-client on Chain Source Code: Address:

MOS Source Code: Address:

OracleNode on MAPO Address:

Light-client on Chain Source Code: Address:

OracleNode on MAPO Address:

OracleNode on Chain Address:

OracleNode on MAPO Address:

OracleNode on Chain Address:

OracleNode on MAPO Address:

Light-client on Chain Address:

OracleNode on MAPO Address:

Light-client on Chain Address:

OracleNode on MAPO Address:

OracleNode on Chain Address:

OracleNode on MAPO Address:

Light-client on Chain Address:

MOS Source Code: Address:

If your chain is EVM-compatible, you can easily connect and integrate with MAP Protocol to achieve omnichain. Read more on .

Now you can easily connect Ton Network and integrate with MAP Protocol to achieve omnichain. Read more on .

You can easily build your omnichain dApps by connecting to MAP Protocol. Read more on .

Ethereum2.0 POS light client
0x6859b2aE7CE9fb0c4FAA71798aC5498B41B42D7A
MAP Relay Chain light client deployed on EVM chains
0x624E6F327c4F91F1Fa6285711245c215de264d49
MOS Message Contracts
0x8C3cCc219721B206DA4A2070fD96E4911a48CB4f
BNB Smart Chain light client
0x14843295C38EaC604dEDe0eDb77e08B460D093D8
MAP Relay Chain light client deployed on EVM chains
0x624E6F327c4F91F1Fa6285711245c215de264d49
MOS Message Contracts
0x8C3cCc219721B206DA4A2070fD96E4911a48CB4f
Polygon Mainnet light client
0x1D621078676D7bdd75FC7F5ebbaBadDC9a65E3c5
MAP Relay Chain light client deployed on EVM chains
0x624E6F327c4F91F1Fa6285711245c215de264d49
MOS Message Contracts
0x8C3cCc219721B206DA4A2070fD96E4911a48CB4f
NEAR light client
0x4464fA3A804b8a44a0aD212eD23155a08f336B34
MAP light client on NEAR
4WUmfmcRYbLfAJyBzXnYPP69iSRuVQ81cJAhZas6Cw1i
MAP Omnichain Service
J1KQdJSNUyBZGwsW3oZ8nFUqv2iLxb3Y8X9DTTJjxJgr
MAP Relay Chain light client delpoyed on EVM chains
0x624E6F327c4F91F1Fa6285711245c215de264d49
MOS Message Contracts
0x8C3cCc219721B206DA4A2070fD96E4911a48CB4f
Klaytn light client
0x91a14b93e4d588879dAE94E2EeE5E1d88b879D81
MAP Relay Chain light client delpoyed on EVM chains
0x624E6F327c4F91F1Fa6285711245c215de264d49
MOS Message Contracts
0x8C3cCc219721B206DA4A2070fD96E4911a48CB4f
Conflux light client
0x3E357098bbBeD2810c9a37FDfB5816067890304a
MAP Relay Chain light client delpoyed on EVM chains
0x624E6F327c4F91F1Fa6285711245c215de264d49
MOS Message Contracts
0xfeb2b97e4efce787c08086dc16ab69e063911380
0x17ecd177019CDD72125659af33446758d7390A42
TCgts2dcdEszFdHnp3D9iKqxGqNrpTYSjQ
PlatON light client
MAP Relay Chain light client deployed on EVM chains
MOS Message Contracts
0x0EBDBB2b94953C1375dbA3C063682a094b4d9780
MAP Relay Chain light client deployed on EVM chains
0x0001805c0b57dbd48b5c5c26e237a135ddc678ae
MOS Message Contracts
0x8C3cCc219721B206DA4A2070fD96E4911a48CB4f
0x10c195Ab0FF99b6711FE8be65469E460d1d4478f
MAP Relay Chain light client deployed on EVM chains
0x0001805c0b57dbd48b5c5c26e237a135ddc678ae
MOS Message Contracts
0xfeB2b97e4Efce787c08086dC16Ab69E063911380
0x667E45a64F7c0e5Ba897C0c072D70cE6B2F73701
MAP Relay Chain light client deployed on EVM chains
0x0001805c0b57dbd48b5c5c26e237a135ddc678ae
0x371717D5ea21f73FEf2a30537571e05f62460CcE
0xA9bDC7D5738d88A6F082b2580A4a425697Da9E5D
0xe656bd52F9953b2688881644e3858fBE4c024627
0x1cbB3ACbD5f8817c75A83A62135A8CF2F86EEd48
0x4030d0e5F10c859268Cd60C18e6DD3F645eea83C
0x0001805c0b57dbd48b5c5c26e237a135ddc678ae
0xe1E918C2157eC00a0b83280C738d3Bb08f172B8B
0x0001805c0b57dbd48b5c5c26e237a135ddc678ae
0xB8560Ed626De95Bad25CcD34264F29682FE677AB
0x6951B909A71cd4189aA21aEfD38dFc3dCee90001
0x5ACa31Fe7314a4c323E83C0F58936Fc40fB47a80
0x0001805c0b57dbd48b5c5c26e237a135ddc678ae
MOS Message Contracts
EQDyD3ICi9YkGdIf19dJHoq-70Ng9lWY9lCbIVM-tfi_yp1v
Integration of MAP with EVM-Compatible Chains
Integration of MAP with TON
OmniApp