接入的链
Last updated
Last updated
Below is MAP Protocol's latest chain connectivity progress and the corresponding contract addresses.
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
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
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
Chain ID: 5566818579631833088
Status: Completed MAP Protocol <-> NEAR
Light-client on MAPO
Source Code: N/A
Address:N/A
Chain ID: 42161
Status: Completed MAP Protocol --> Arbitrum One
Chain ID: 8721
Status: Completed MAP Protocol <-> Klaytn
Chain ID:1030
Status: Completed MAP Protocol <-> Conflux
Chain ID: 728126428
Status: MAP Protocol <--> Tron
Chain ID: 210425
Status: Coming soon
Chain ID: 10
Status: MAP Protocol --> OP Mainnet
Chain ID: 8453
Status: MAP Protocol <--> Base
MOS: 0xfeB2b97e4Efce787c08086dC16Ab69E063911380
Chain ID: 59144
Status: MAP Protocol <--> Linea
Chain ID: 324
Status: MAP Protocol <--> zkSync
Chain ID: 4200
Status: MAP Protocol <--> Merlin
Chain ID: 81457
Status: MAP Protocol <--> Blast
Chain ID: 534352
Status: MAP Protocol <--> Scroll
Chain ID: 2649
Status: MAP Protocol <--> AINN
Chain ID: 223
Status: MAP Protocol <--> B²
Chain ID: 5000
Status: MAP Protocol <--> Mantle
OracleNode on Chain
Address: 0x1ceB1E03E9a23f5ACee598c42521EF87f24d6fCB
Chain ID: 810180
Status: MAP Protocol <--> zkLink
Planning
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:
OracleNode on Chain
Address:
OracleNode on MAPO
Address:
Light-client on Chain
Address:
OracleNode on MAPO
Address:
If your chain is EVM-compatible, you can easily connect 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 .