MAPO Developer Docs
LearnDevelopRunWhitePaperBRC-201
English
English
  • Overview
  • Learn
    • About MAP Protocol
      • Background
      • Introduction of MAP Protocol
      • History of MAP Protocol
    • Comparison with other cross-chain models
      • MAP Protocol vs Cosmos & Polkadot
      • MAP vs other cross-chain solutions without relay chain
    • Technical Mechanism
      • MAP Protocol's Technical Mechanism
      • Three-layer Architecture
      • MAP Protocol Layer
        • Concept
        • Isomorphism with All Chains
        • Verification & Maintenance Network
      • MAP Omnichain Service (MOS) Layer
      • MAPO Application Layer
      • Peer-to-Peer Cross-chain Technology with ZK-enabled Light Clients
      • Interact with Bitcoin
    • Gas Fee Model
    • DAO
    • Construction of MAP Protocol
      • Developers
      • Validators
      • Maintainers
      • Messengers
      • Liquidity providers
      • End users
    • Tokenomics
    • Purchase $MAP
  • Develop
    • MAP Relay Chain
      • Getting Started
        • Build
        • Make Private Chain
        • How To Vote
        • How To Withdraw
        • Integrate an Exchange
        • Integrate MAP Relay Chain with EVM-Compatible Chains
      • Consensus
        • Overview
        • Proof-of-Stake
        • Validator
          • Validator
          • Locked MAP
        • Election
        • Rewards
        • Aggregated Seal
      • Contracts
        • Precompiled Contracts
        • Genesis Contracts
          • ABI
            • AccountsABI
            • ElectionABI
            • EpochRewardsABI
            • LockedGoldABI
            • ValidatorsABI
          • Deploy
      • Marker
        • Genesis
        • Validator
        • Vote
        • ContractOwner
        • Common
      • Account-Abstraction
    • Light Client
      • Verification based on Light Client
      • MAPO Light Client
        • EVM Chains
        • Near
      • Light Clients
        • Client Manager
        • BNB Smart Chain
        • Near Protocol
        • Polygon(Matic)
        • Ethereum 2.0
        • Klaytn
        • Conflux)
      • Maintainer
    • MAP Omnichain Service (MOS)
      • MOS Message Guides
        • How It Works
        • How To Use
        • EVM Chains Contract
      • MCS Guides
        • How It Works
        • How To Use
          • How To On Evm Chains
          • How To On Near Protocol
        • Relay Chain Contract
        • EVM Chains Contract
        • Near Protocol Contract
      • Messenger
      • API
    • OmniChain Examples
      • OmniApp
      • OmniDictionary
    • API & SDK
      • Butter SDK
      • Atlas JSON RPC
      • Atlas Consensus API
      • MAP Scan API
    • Connected Chains and Corresponding Addresses
  • Run
    • How To Become A New Validator
    • How To Become A New Validator[advanced]
    • Withdraw
Powered by GitBook
On this page

Was this helpful?

  1. Learn
  2. Technical Mechanism

MAP Protocol's Technical Mechanism

PreviousTechnical MechanismNextThree-layer Architecture

Last updated 2 years ago

Was this helpful?

While cross-chain bridges can be easily built with MAP Protocol, MAP Protocol itself tackles a more fundamental problem and pursues a larger vision: boosting the whole cross-chain ecosystem by building an omnichain network infrastructure. Any dApp built with the infrastructure utomatically inherits the omnichain nature of MAP Protocol without requiring the developers to tackle the error-prone cross-chain communications. With the technical threshold of building omnichain dApp reduced, the ecosystem shall thrive.

  1. MAP Protocol is structured in three layers: Protocol Layer, Omnichain Services Layer (MOS), and Application Layer.

  2. MAP Protocol achieves omnichain interoperability with all EVM and non-EVM chains by deploying cross-chain execution and verification via on-chain smart contracts, and cross-chain messenger inter-chain program.

  3. MAP Protocol's cross-chain verification network has security finality by adopting the Light-client independent self-verification mechanism.

  4. MAP Relay Chain is fully EVM compatible built upon Proof-of-Stake mechanism and **Byzantine Fault Tolerant consensus.

  5. MAP Relay Chain accomplished heterogeneous expansion on the EVM level, which simplified the complexity of engineering and minimized the gas fee for cross-chain verification between heterogeneous chains.

  6. By connecting with MAP Relay Chain, EVM and non-EVM chains form a cross-chain execution and verification network.

  7. MAP Protocol provides SDK for the inter-chain communication component - Messenger to dApp developers. Each dApp can have its own Messenger and tailor-make their reward scheme, which facilitates cross-chain transactions to be completed.

  8. MAP Protocol provides developers with MAP Cross-chain Services similar to Google GMS. It is convenient for developers to develop and share omnichain asset liquidity and data.

  9. MAP Protocol supports both assets and data cross-chain.

  10. MAP Relay Chain supports the development of all omnichain dApps, including omnichain oracle, omnichain swap, cross-chain bridge for tokens and NFTs, decentralized derivatives, omnichain DAO, and omnichain GameFi, etc.

Technical Illustration of MAP Protocol

Developers can deploy omnichain dApps on MAP Relay Chain to achieve interoperability.