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
  • Components
  • Bitcoin Light Client
  • Omni-chain Service
  • Staking Contract
  • Roles
  • Maintainer
  • Validator
  • Inspector

Was this helpful?

  1. Learn
  2. Technical Mechanism

Interact with Bitcoin

PreviousPeer-to-Peer Cross-chain Technology with ZK-enabled Light ClientsNextGas Fee Model

Last updated 7 months ago

Was this helpful?

Here's a breakdown of a solution to MAP Protocol interact with Bitcoin:

Components

Bitcoin Light Client

A Bitcoin SPV (Simplified Payment Verification) contract will be deployed on the MAP Protocol to synchronize Bitcoin block headers. This contract will allow verification of Bitcoin on-chain transactions by leveraging SPV proofs, ensuring the validity of cross-chain transactions involving Bitcoin trustlessly.

Omni-chain Service

An Omni-chain service contract will be deployed on the MAP Protocol to facilitate cross-chain interactions between Bitcoin and other blockchain networks. The contract will process and manage cross-chain requests, such as transfers and other state changes, between Bitcoin and the supported chains.

Staking Contract

A staking contract will be established to allow participants to stake $MAPO and become validator nodes. If validators behave maliciously or act against protocol rules, they will be penalized via a slashing mechanism in the staking contract. Staked assets will be at risk of punishment in the event of malicious behavior. Validators are responsible for verifying and processing cross-chain transactions.

Roles

Maintainer

Maintainers are responsible for monitoring the Bitcoin blockchain. They will submit block headers to the Bitcoin Light Client contract on MAP Protocol and relay cross-chain transactions from Bitcoin to the Omnichain service. Maintainers play a key role in ensuring the timely and accurate submission of Bitcoin data to the MAP Protocol.

Validator

Validators listen for cross-chain transaction requests emitted by the Omni-chain service. Once a cross-chain transaction is initiated, validators, using MPC (Multi-Party Computation) protocols, collaboratively generate and sign the cross-chain transaction destined for the Bitcoin network. Validators then submit the finalized Bitcoin transaction to the Bitcoin blockchain, ensuring the cross-chain interaction is processed.

Now Validators are selected from trusted ecosystem partners, ensuring they have an active role in managing and securing cross-chain interactions.

Inspector

The Inspector is responsible for monitoring the behavior of validators. It listens for validator actions, particularly those related to cross-chain transactions. If the Inspector detects malicious behavior or an invalid transaction submitted by a validator, it submits the evidence of the wrongdoing to the staking contract. The staking contract will then execute the penalty mechanism to slash the stake of the offending validator, ensuring protocol security and integrity.

Interact with Bitcoin