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
  • MAP Protocol Layer
  • MAP Omnichain Service (MOS) Layer
  • MAPO Application Layer

Was this helpful?

  1. Learn

Construction of MAP Protocol

MAP Protocol Layer

  • Validator: Validator is the foundation of the MAP Relay Chain. Community members can stake $MAPO and build a node with the required computing power to run a validator. Community members can also delegate their $MAPO to other validator operators.

  • Maintainer: The value of the maintainer is to update the status of the Light-client deployed on the target chain so that the verification network can run smoothly. When the maintainer updates the Light-client, a transaction must be written on-chain, resulting in a gas fee payment. Because of this, MAP Protocol's economic model has designed a portion separately to incentivize and compensate Maintainers. Running as a maintainer requires computation power, sufficient fund flow to prepay the gas fees with the target chain's token, and staking of $MAPO.

MAP Omnichain Service (MOS) Layer

  • Liquidity provider: Community members can provide liquidity to Vaults on each chain through Dapps deployed in the MAP ecosystem. Incentives are provided directly by each Dapp.

  • Messenger: Running as a messenger requires a sufficient amount of gas fee for the MAP Relay Chain ($MAPO) and the target chains (native token). Messengers are incentivized by each Dapp.

MAPO Application Layer

  • End Users: Community members can participate through various types of Dapps in the MAP ecosystem and get rewards.

PreviousDAONextDevelopers

Last updated 1 year ago

Was this helpful?