MAPO Developer Docs
  • MAPO Developer Docs
  • Base
    • MAPO Introduction
    • MAPO token
    • Omnichain DAPP
    • Differences Between Omnichain Applications and Single or Multi-Chain Applications
    • Differences Between Third-Party Trusted Cross-Chain and Peer-to-Peer Cross-Chain Solutions
    • BTC layer2
      • brc-201
    • Oracle
      • Supra: Decentralized Oracle on MAP Protocol
    • Account
    • Transactions
    • block
    • MPT tree
    • RLP
    • Gas fee
    • Cross Chain Message
    • light client
      • MAPO light client
    • MOS
      • MOS interface and functions
      • deploy MOS
      • Messenger
    • map-relay-chain(atlas)
      • atlas architecture
        • atlas architecture
        • atlas genesis
          • genesis config
          • genesis contract
            • ABI
              • Accounts
              • Election
              • EpochRewards
              • LockedGold
              • Validators
            • address
            • deploy
        • precompile-contract
        • protocol
          • Proof of Stake
          • consensus
          • election
          • rewards
          • governance
      • deploy atlas
        • run atlas
        • run atlas(archive)
        • run atlas(bootnodes)
        • run atlas(validator)
        • run atlas(RPC)
      • Marker tool
        • Genesis
        • Validator
        • Vote
        • Common
      • make private network(atlas)
      • public service
        • public network
      • example
        • how-to-vote
        • how-to-withdraw
        • how-to-become-a-new-validator
        • how-to-become-a-new-validator(advanced)
    • Compass(maintainer,messenger)
      • Compass - arch and model
      • Compass - config
      • Compass - deploy
      • Compass secondary development - define your own routing service based on compass
  • MAPO Stack
    • stack
      • Connected Chains and Corresponding Addresses
    • Compatible-EVM
      • Smart Contracts Language
      • Smart Contracts Anatomy
      • Smart Contracts Libraries
      • Smart Contracts Compile
      • Smart Contracts Testing
      • Smart Contracts Deploy
      • Smart Contracts Composability
      • Smart Contracts Security
      • Formal-Verification
      • Frameworks
      • dev-network
    • MAPO Implement Cross-chain Interoperability
      • integration of MAP with EVM-Compatible Chains
        • light client verify
        • light client update state
        • MOS
      • integration of MAP with TON Network
      • integration of MAP with Non-EVM-Compatible Chains
        • light client verify
        • light client update state
        • MOS
    • How to develop cross-chain applications
    • light client address
    • SDK/API
      • MOS interface
      • Light client interface
      • Atlas RPC
        • json-rpc
          • atlas json rpc
          • atlas consensus rpc
        • javaScript sdk
        • go-sdk
      • Backend API
        • SCAN API
  • Zero-Knowledge Proof
    • zk proof
Powered by GitBook
On this page
  • What is a Single-Chain Application?
  • What is a Multi-Chain Application?
  • What is a Full-Chain Application?
  1. Base

Differences Between Omnichain Applications and Single or Multi-Chain Applications

There are hundreds of blockchains worldwide, and this number continues to grow with the development of the industry. Each blockchain is isolated, which can pose a dilemma for developers when deciding on which blockchain to deploy their applications. Deploying smart contracts on multiple chains separately increases the workload for developers and creates difficulties for users of decentralized applications in conducting cross-chain operations.

What is a Single-Chain Application?

A single-chain application involves deploying smart contracts on a single blockchain. Developers commonly choose a well-considered blockchain for initial deployment. However, this approach often misses the opportunity for users on other blockchains to participate in the application. With the MAP Protocol option, the need to make a single-chain decision from the outset becomes unnecessary.

What is a Multi-Chain Application?

Multi-chain applications refer to the deployment of smart contracts on different blockchains. As projects grow and attract more users, developers need to consider user convenience and how to attract participation from users on uncovered blockchains. However, deploying contracts separately, apart from complex development, leads to isolated blockchains where users cannot interact within the same application. This poor user experience can ultimately lead to user attrition to competitors.

What is a Full-Chain Application?

A full-chain application represents an entirely different development paradigm. Developers only need to use the MAP Protocol as a development tool. They can automatically cover all major blockchains through MAP Protocol's infrastructure and related developer tools, ensuring interoperability. Users remain agnostic to the underlying blockchains. This approach bypasses the development stage from single-chain applications to multi-chain applications, allowing developers to achieve a one-time comprehensive solution in terms of infrastructure.

PreviousOmnichain DAPPNextDifferences Between Third-Party Trusted Cross-Chain and Peer-to-Peer Cross-Chain Solutions

Last updated 1 year ago