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

• OracleNode on MAPO Address:0x17ecd177019CDD72125659af33446758d7390A42

• MOS Source Code: MOS Message Contracts Address: TAR515UoMxTa2ruua6KqnXDwPJQEu66RVU

• Chain ID: 728126428

• Status: 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

• OracleNode on MAPO Address:0x0EBDBB2b94953C1375dbA3C063682a094b4d9780

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

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

• Chain ID: 10

• Status: MAP Protocol --> OP Mainnet

Base

• OracleNode on MAPO Address:0x10c195Ab0FF99b6711FE8be65469E460d1d4478f

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

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

• Chain ID: 8453

• Status: MAP Protocol <--> Base

Linea

• OracleNode on MAPO Address:0x667E45a64F7c0e5Ba897C0c072D70cE6B2F73701

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

• MOS: 0xfeB2b97e4Efce787c08086dC16Ab69E063911380

• Chain ID: 59144

• Status: MAP Protocol <--> Linea

zkSync

• OracleNode on MAPO Address:0x371717D5ea21f73FEf2a30537571e05f62460CcE

• OracleNode on Chain Address: 0xA9bDC7D5738d88A6F082b2580A4a425697Da9E5D

• Chain ID: 324

• Status: MAP Protocol <--> zkSync

Merlin

• OracleNode on MAPO Address:0xe656bd52F9953b2688881644e3858fBE4c024627

• OracleNode on Chain Address: 0x1cbB3ACbD5f8817c75A83A62135A8CF2F86EEd48

• Chain ID: 4200

• Status: MAP Protocol <--> Merlin

Blast

• OracleNode on MAPO Address:0x4030d0e5F10c859268Cd60C18e6DD3F645eea83C

• Light-client on Chain Address: 0x0001805c0b57dbd48b5c5c26e237a135ddc678ae

• Chain ID: 81457

• Status: MAP Protocol <--> Blast

Scroll

• OracleNode on MAPO Address:0xe1E918C2157eC00a0b83280C738d3Bb08f172B8B

• Light-client on Chain Address: 0x0001805c0b57dbd48b5c5c26e237a135ddc678ae

• Chain ID: 534352

• Status: MAP Protocol <--> Scroll

AINN

• OracleNode on MAPO Address:0xB8560Ed626De95Bad25CcD34264F29682FE677AB

• OracleNode on Chain Address: 0x6951B909A71cd4189aA21aEfD38dFc3dCee90001

• Chain ID: 2649

• Status: MAP Protocol <--> AINN

B² network

• OracleNode on MAPO Address:0xab897386F696eA34D6968A4058547F726Eb245Aa

• OracleNode on Chain Address: 0x6951B909A71cd4189aA21aEfD38dFc3dCee90001

• Chain ID: 223

• Status: MAP Protocol <--> B²

Mantle

• OracleNode on MAPO Address:0x5ACa31Fe7314a4c323E83C0F58936Fc40fB47a80

• Light-client on Chain Address: 0x0001805c0b57dbd48b5c5c26e237a135ddc678ae

• Chain ID: 5000

• Status: MAP Protocol <--> Mantle

zkLink

• OracleNode on MAPO Address:0xD017252b2933Ec3723BdEdfDF1C891e4583955bd

• OracleNode on Chain Address: 0x1ceB1E03E9a23f5ACee598c42521EF87f24d6fCB

• Chain ID: 810180

• Status: MAP Protocol <--> zkLink

Solana

• Planning

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.