Omnichain Layer of Web3.0
Built on Bitcoin Level Peer-to-Peer Cross-chain Communication Technology
Code is law: MAP Protocol is built upon light clients technology defined by Satoshi Nakamoto in Simplified Pay Verification (SPV). Truly peer-to-peer without any privileged third parties: Verifying the validity of a cross-chain request relies solely on the authenticity of the source chain's occurrence, instead of any third-party off-chain roles. Refactor light clients with ZK Technology: ZK was introduced to optimize light clients construction and cross-chain verification efficiency; thus, the Bitcoin level peer-to-peer cross-chain interoperability can be achieved in an effective way.
Satoshi Nakamoto："A purely peer-to-peer version of electronic cash would allow online payments to be sent directly from one party to another without going through a financial institution. Digital signatures provide part of the solution, but the main benefits are lost if a trusted third party is still required to prevent double-spending. We propose a solution to the double-spending problem using a peer-to-peer network."
For an open and decentralized financial system, placing trust in a few chosen third parties is the primary cause of cross-chain hacks; Cross-chain solutions constructed using off-chain consensus offer reduced gas fees and faster transaction speeds, but they also entail collusion risks. With Light Client technology defined by Satoshi Nakamoto and cost-efficient ZK technology, MAP Protocol achieves Bitcoin-level peer-to-peer cross-chain communication. Users and developers only need to trust the code and utilize MAP Protocol in a similar manner as they would with the Bitcoin network.
Build Omnichain dApps
View Docs >
Peer-to-Peer Cross-chain Technology
Satoshi Nakamoto："It is possible to verify payments without running a full network node. A user only needs to keep a copy of the block headers of the longest proof-of-work chain, which he can get by querying network nodes until he's convinced he has the longest chain, and obtain the Merkle branch linking the transaction to the block it's timestamped in. He can't check the transaction for himself, but by linking it to a place in the chain, he can see that a network node has accepted it, and blocks added after it further confirm the network has accepted it."
More details +
MAP Protocol has connected with many major L1s and is actively expanding its connectivity to more L1s and L2s. To learn more details, please view
Latest cross-chain progress
Use Case Examples
An open, peer-to-peer cross-chain network that brings unique decentralized DeFi experiences to both users and developers. Below are some use case examples.
Interoperable Cross-chain Smart Contracts
Regardless of which chain users are on, they can use DeFi products on other chains without going through complex bridging. Similarly, developers do not have to migrate different dApp’s smart contracts but can build seamlessly like they’re using Cloud services.
When users want to buy an NFT or an item on-chain, they often find themselves not having the required token. In the real world, users often encounter long processing time and high transaction fees for cross-border transactions. However, those can all be resolved with Omnichain Payment that can connect different chains, the on-chain world and the real world.
Omnichain Token Issuance
When a project issues tokens, it often has to deploy separate contracts on different chains. This results in fragmented token issuance and may lead to problematic ledger alignment. With MAP Protocol, however, projects can achieve omnichain coverage at the beginning of token issuance, and the ledgers of different chains will be aligned automatically, so that users can seamlessly move a token from one chain to another.
User AI data generated by interacting with AIGC services can be stored on decentralized storage Layer 1 (L1), but are not tradable. Through peer-to-peer cross-chain messaging, user AI data can be tradded on blockchains with popular DeFi markets.
More details +