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
  • prerequisites
  • how-to-deploy-a-smart-contract
  • related-tools
  1. MAPO Stack
  2. Compatible-EVM

Smart Contracts Deploy

PreviousSmart Contracts TestingNextSmart Contracts Composability

Last updated 1 year ago

You need to deploy your smart contract for it to be available to users of an MAPO-Relay-Chain. The following MAPO-Relay-Chain is collectively referred to as MAPO.

To deploy a smart contract, you merely send an MAPO coin transaction containing the compiled code of the smart contract without specifying any recipient.

prerequisites

You should understand , and the before deploying smart contracts.

Deploying a contract also costs MAPO coins (MAPO) since they are stored on the blockchain, so you should be familiar with on MAPO.

Finally, you'll need to compile your contract before deploying it, so make sure you've read about .

how-to-deploy-a-smart-contract

what-youll-need

  • your contract's bytecode – this is generated through

  • MAPO coins for gas – you'll set your gas limit like other transactions so be aware that contract deployment needs a lot more gas than a simple MAPO coins transfer

  • a deployment script or plugin

  • access to an , either by running your own, connecting to a public node

steps-to-deploy

The specific steps involved will depend on the tooling you use. For an example, check out the or . These are two of the most popular tools for smart contract deployment, which involve writing a script to handle the deployment steps.

Once deployed, your contract will have an MAPO address.

related-tools

Remix - Remix IDE allows developing, deploying and administering smart contracts for Ethereum like blockchains

Tenderly - Web3 development platform that provides debugging, observability, and infrastructure building blocks for developing, testing, monitoring, and operating smart contracts

Hardhat - A development environment to compile, deploy, test, and debug your Ethereum software

Truffle - A development environment, testing framework, build pipeline, and other tools.

MAPO networks
transactions
anatomy of smart contracts
gas and fees
compiling smart contracts
compilation
MAPO node
Hardhat documentation on deploying your contracts
Truffle documentation on networks and app deployment
Remix
tenderly.co
Docs
GitHub
Discord
hardhat.org
Docs on deploying your contracts
GitHub
Discord
trufflesuite.com
Docs on networks and app deployment
GitHub