Connected Chains and Corresponding Addresses

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 MAP Relay Chain will need to deploy light clients on each other's chains respectively, as well as MAP Omnichian Service (MOS) onto the target chain.

Ethereum

• Light-client on MAPO Source Code: Ethereum2.0 POS light client Address: 0x6859b2aE7CE9fb0c4FAA71798aC5498B41B42D7A

• Light-client on Chain Source Code: MAP Relay Chain light client deployed on EVM chains Address: 0x624E6F327c4F91F1Fa6285711245c215de264d49

• MOS Source Code: MOS Message Contracts Address: 0x8C3cCc219721B206DA4A2070fD96E4911a48CB4f

• Chain ID: 1

• Status:Completed MAP Protocol <-> Ethereum

BNB Smart Chain

• Light-client on MAPO Source Code: BNB Smart Chain light client Address: 0x14843295C38EaC604dEDe0eDb77e08B460D093D8

• Light-client on Chain Source Code: MAP Relay Chain light client deployed on EVM chains Address: 0x624E6F327c4F91F1Fa6285711245c215de264d49

• MOS Source Code: MOS Message Contracts Address: 0x8C3cCc219721B206DA4A2070fD96E4911a48CB4f

• Chain ID: 56

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

Polygon Mainnet

• Light-client on MAPO Source Code: Polygon Mainnet light client Address: 0x1D621078676D7bdd75FC7F5ebbaBadDC9a65E3c5

• Light-client on Chain Source Code: MAP Relay Chain light client deployed on EVM chains Address: 0x624E6F327c4F91F1Fa6285711245c215de264d49

• MOS Source Code: MOS Message Contracts Address: 0x8C3cCc219721B206DA4A2070fD96E4911a48CB4f

• Chain ID: 137

• Status: Completed MAP Protocol <-> Polygon Mainnet

NEAR

• Light-client on MAPO Source Code: NEAR light client Address: 0x4464fA3A804b8a44a0aD212eD23155a08f336B34

• Light-client on Chain Source Code: MAP light client on NEAR Address: 4WUmfmcRYbLfAJyBzXnYPP69iSRuVQ81cJAhZas6Cw1i

• MOS Source Code: MAP Omnichain Service Address: J1KQdJSNUyBZGwsW3oZ8nFUqv2iLxb3Y8X9DTTJjxJgr

• Chain ID: 5566818579631833088

• Status: Completed MAP Protocol <-> NEAR

Arbitrum One

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

• Light-client on Chain Source Code: MAP Relay Chain light client delpoyed on EVM chains Address: 0x624E6F327c4F91F1Fa6285711245c215de264d49

• MOS Source Code: MOS Message Contracts Address: 0x8C3cCc219721B206DA4A2070fD96E4911a48CB4f

• Chain ID: 42161

• Status: Completed MAP Protocol --> Arbitrum One

Klaytn

• Light-client on MAPO Source Code: Klaytn light client Address:0x91a14b93e4d588879dAE94E2EeE5E1d88b879D81

• Light-client on Chain Source Code: MAP Relay Chain light client delpoyed on EVM chains Address: 0x624E6F327c4F91F1Fa6285711245c215de264d49

• MOS Source Code: MOS Message Contracts Address: 0x8C3cCc219721B206DA4A2070fD96E4911a48CB4f

• Chain ID: 8721

• Status: Completed MAP Protocol <-> Klaytn

Conflux

• Light-client on MAPO Source Code: Conflux light client Address:0x3E357098bbBeD2810c9a37FDfB5816067890304a

• Light-client on Chain Source Code: MAP Relay Chain light client delpoyed on EVM chains Address: 0x624E6F327c4F91F1Fa6285711245c215de264d49

• MOS Source Code: MOS Message Contracts Address: 0xfeb2b97e4efce787c08086dc16ab69e063911380

• Chain ID:1030

• Status: Completed MAP Protocol <-> Conflux

Tron

• MOS Source Code: MOS Message Contracts Address: TAR515UoMxTa2ruua6KqnXDwPJQEu66RVU

• Chain ID: 728126428

• Status: Developing MAP Protocol <--> Tron

PlatON Mainnet

• Light-client on MAPO Source Code: PlatON light client Address:Coming soon

• Light-client on Chain Source Code: MAP Relay Chain light client deployed on EVM chains Address: Coming soon

• MOS Source Code: MOS Message Contracts Address: Coming soon

• Chain ID: 210425

• Status: Coming soon

OP Mainnet

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

• Light-client on Chain Source Code: MAP Relay Chain light client deployed on EVM chains Address: 0x624E6F327c4F91F1Fa6285711245c215de264d49

• MOS Source Code: MOS Message Contracts Address:0x8C3cCc219721B206DA4A2070fD96E4911a48CB4f

• Chain ID: 10

• Status: Coming soon MAP Protocol --> OP Mainnet

Base

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

• Light-client on Chain Source Code: MAP Relay Chain light client deployed on EVM chains Address: 0x624E6F327c4F91F1Fa6285711245c215de264d49

• MOS Source Code: MOS Message Contracts Address: 0x8C3cCc219721B206DA4A2070fD96E4911a48CB4f

• Chain ID: 8453

• Status: Coming soon MAP Protocol --> Base

Linea

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

• Light-client on Chain Source Code: MAP Relay Chain light client deployed on EVM chains Address: 0x624E6F327c4F91F1Fa6285711245c215de264d49

• MOS: Coming soon

• Chain ID: 59144

• Status: Coming soon

Avalanche C-Chain

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

• Light-client on Chain Source Code: MAP Relay Chain light client deployed on EVM chains Address: 0x624E6F327c4F91F1Fa6285711245c215de264d49

• MOS: Coming soon

• Chain ID: 43114

• Status: Coming soon

Boba Network

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

• Light-client on Chain Source Code: MAP Relay Chain light client deployed on EVM chains Address: 0x624E6F327c4F91F1Fa6285711245c215de264d49

• MOS: Coming soon

• Chain ID: 288

• Status: Coming soon

Metis Andromeda

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

• Light-client on Chain Source Code: MAP Relay Chain light client deployed on EVM chains Address: 0x624E6F327c4F91F1Fa6285711245c215de264d49

• MOS:

• Chain ID: 1088

• Status: Coming soon

zkSync

• Planning

zkEvm(Polygon)

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

• Light-client on Chain Source Code: MAP Relay Chain light client deployed on EVM chains Address: 0x624E6F327c4F91F1Fa6285711245c215de264d49

• MOS:

• Chain ID: 1101

• Status: Coming soon

Merlin

• MOS Source Code: MOS Message Contracts Address: 0xfeB2b97e4Efce787c08086dC16Ab69E063911380

• Chain ID: 4200

• Status: Developing MAP Protocol <--> Merlin

Blast

• MOS Source Code: MOS Message Contracts Address: 0xfeB2b97e4Efce787c08086dC16Ab69E063911380

• Chain ID: 81457

• Status: Developing MAP Protocol <--> Blast

Scroll

• Planning

Solana

• Planning

Filecoin

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

• Light-client on Chain Source Code: MAP Relay Chain light client deployed on EVM chains Address: 0x624E6F327c4F91F1Fa6285711245c215de264d49

• MOS: Coming soon

• Chain ID: 314

• Status: Coming soon

xrpl-evm-sidechain

• Coming soon

EthereumPoW

• Coming soon

Gnosis Chain

• Coming soon

ICP(DFINITY)

• Coming soon

How to integrate MAP Protocol with EVM-Compatible Chains

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

How to build a dApp with MAP Protocol

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