MAP Protocol is the omnichain layer for Web3 with provably secure cross-chain communication built on Light-client and zk-SNARK technology. MAP provides cross-chain infrastructure to public chains and dApps by connecting both EVM with non-EVM chains. Developers can access a full suite of SDKs so their dApps can easily become omnichain applications.
The repository has the following packages (sub projects):
- Management protocol - MAP Protocol management conctracts on MAP Relay Chain
- MAP Relay Chain light client - MAP Relay Chain light client implementation on all chains
- EVM chains - MAP Relay Chain light client on EVM chains
- Near - map relay chain light client on Near Protocol
- light clients on MAP - scripts for deploying and managing testnets
- BNB Smart Chain light client - BNB smart chain light client on MAP Relay Chain
- Near light client - Near Protocl light client on map relay chain
- MAP Omnichain Service - MAP omnichain Service reference implementation, mos contracts will be deplyed on every chain to achieve cross-chain interoperablity
- MOS on evm chains - mos on evm chains
- MOS on near
-
Relay Chain Protocol
-
MAP Light Client
-
Light Clients on MAP
-
MOS Relay contracts fee, register, relay, proxy set fee
-
MOS contracts on other chains mcs, proxy relay register (chain type, address) setrelay
-
token register (map <-> chain) relay: a. create map token if needed b. set auth token(if needed) c. create map vault d. bind vault and token e. set fee f. relay token register (decimal, chain token)
mos: a. mos set auth token b. mos register token
-
token update a. relay set fee b. relay token register (decimal, chain token) c. mos set auth token if neened d. mos register token
-
token deploy a.