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
  • Introduction of MAP Protocol
  • Features of MAP Protocol

Was this helpful?

  1. Learn
  2. About MAP Protocol

Introduction of MAP Protocol

Introduction of MAP Protocol

MAP Protocol is the omnichain network for an interoperable Web3 with five main features: Security-Finality, All-Chain Coverage, Instant Confirmation, Minimum Cost, and Developer-Ready.

MAP Protocol provides instant confirmation for omnichain transactions and verification finality by light-client, offers SDK and API for low-code deployment, proactively embeds other chains' algorithms as pre-compiled contracts in the EVM layer of MAP Relay Chain, and maintains a cost-efficient network.

Nowadays, general chains, such as Ethereum, Avalanche, Flow, have their own respective territory; and dedicated chains, such as IoTex, NKN, are also thriving. Omnichain network, an infrastructure to connect them all, is the future. Together with worldwide developers, MAP Protocol is the dawn of a new omnichain age.

Developers can easily build their omnichain applications deployed on any chain in just two steps:

  1. Build inter-chain messenger.

  2. Interact with on-chain vault and data through our SDK.

Features of MAP Protocol

Security-Finality

Guarantee blockchain-level security through an independent self-verification network formed by light clients on every public blockchain.

All-Chain Coverage

Embed heterogeneous chains' signing and hashing algorithm into the EVM layer of the MAP Relay Chain to ensure seamless communication between all chains.

Instant Confirmation

Inter-chain communication programs and on-chain smart contracts work together efficiently to ensure that speed is only related to each chain's block time.

Minimum Cost

MAP Protocol only charge the gas fee of MAP Relay Chain and other related chains with no additional cost.

Developer-Ready

Through MAP Omnichain Service (MOS) deployed on and between public chains, dAPPs can share the liquidity of MOS's Vaults on different chains, and customize the entry threshold and incentive model of inter-chain program: messenger. Alternatively, we can use the MOS open source code to build dAPP-related Omnichain components.

PreviousBackgroundNextHistory of MAP Protocol

Last updated 1 year ago

Was this helpful?