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
  • Mainnet Address
  • Altchains light clients on MAP Relay Chain Mainnet
  • MAPO Mainnet (chain id 22776) Light Node
  • Testnet Address
  • Altchains light clients on MAP Makalu Testnet
  • MAPO Makalu Testnet (chain id 212) Light Node

Was this helpful?

  1. Develop

Light Client

Mainnet Address

Altchains light clients on MAP Relay Chain Mainnet

Network
Chain ID
Type
Contract Address

client manager

BSC

56

light client

Polygon(Matic)

137

light client

Near

5566818579631833088

light client

MAPO Mainnet (chain id 22776) Light Node

Network
Contract Address

BSC

Polygon(Matic)

Near

Testnet Address

Altchains light clients on MAP Makalu Testnet

Network
Chain ID
Type
Contract Address

client manager

BSC Testnet

97

light client

Polygon Mumbai

80001

light client

Near Testnet

5566818579631833089

light client

MAPO Makalu Testnet (chain id 212) Light Node

Network
Contract Address

BSC Testnet

Polygon Mumbai

Near Testnet

PreviousAccount-AbstractionNextVerification based on Light Client

Last updated 2 years ago

Was this helpful?

0x624E6F327c4F91F1Fa6285711245c215de264d49
doc
0x14843295C38EaC604dEDe0eDb77e08B460D093D8
doc
0x1D621078676D7bdd75FC7F5ebbaBadDC9a65E3c5
doc
0x4464fA3A804b8a44a0aD212eD23155a08f336B34
doc
0x624E6F327c4F91F1Fa6285711245c215de264d49
doc
0x624E6F327c4F91F1Fa6285711245c215de264d49
doc
client2.cfac.mapprotocol.near
doc
0xDD3A69f8f59d892476B0be0260932b4f8d8268Ff
doc
0xB610a58ff65AC5E5070B6f16Ddf5dc42438419f9
doc
0xBE6d8ddE766D00f8c894FeECbf5B12a5486d73B5
doc
0x04BA4464a5e8bD3D1a3985c8a09C1346F48A94f8
doc
0xdB913e87608e3d91C6F0b52E97a6760E7661B8f6
doc
0x05634BdfbDa8aC4653Ff0655d71719F61A0922C4
doc
client3.cfac2.maplabs.testnet
doc