Connected Chains and Corresponding Addresses
Ethereum
Status:Completed MAP Protocol <-> Ethereum
BNB Smart Chain
Status: Completed MAP Protocol <-> BNB Smart Chain
Polygon Mainnet
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
Status: Completed MAP Protocol --> Arbitrum One
Klaytn
Status: Completed MAP Protocol <-> Klaytn
Conflux
Status: Completed MAP Protocol <-> Conflux
Tron
Status: MAP Protocol <--> Tron
PlatON Mainnet
OP Mainnet
Status: MAP Protocol --> OP Mainnet
Base
Status: MAP Protocol <--> Base
Linea
MOS: 0xfeB2b97e4Efce787c08086dC16Ab69E063911380
Status: MAP Protocol <--> Linea
zkSync
Status: MAP Protocol <--> zkSync
Merlin
Status: MAP Protocol <--> Merlin
Blast
Status: MAP Protocol <--> Blast
Scroll
Status: MAP Protocol <--> Scroll
AINN
Status: MAP Protocol <--> AINN
Mantle
Status: MAP Protocol <--> Mantle
Solana
How to integrate MAP Protocol with EVM-Compatible Chains
How to build a dApp with MAP Protocol
Below is MAP Protocol's latest chain connectivity progress and the corresponding contract addresses. In order to integrate with MAP Protocol's omnichain ecosystem, both the target chain and the will need to deploy light clients on each other's chains respectively, as well as onto the target chain.
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:
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:
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:
MOS
Source Code:
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:
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 .
