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
  • Clone the Code Repository and Build
  • Running the Node
  1. Base
  2. map-relay-chain(atlas)
  3. deploy atlas

run atlas

Running your own node provides various benefits, opens up new possibilities, and helps support the ecosystem. This page will guide you on how to start your own node and participate in transaction validation.

Prerequisites

Hardware Requirements

Hardware requirements vary depending on the type of node but are generally not very high. Here are the recommended configurations:

  1. Machine Configuration MAP is a proof-of-stake network, which has different hardware requirements compared to proof-of-work networks. Proof-of-stake consensus is less demanding on CPUs but more sensitive to network connectivity and latency. Here is a standard requirement list for running a validator on the MAP network:

    • Memory: 16 GB RAM

    • CPU: Quad-core 2.5 GHz (64-bit)

    • Disk: 256 GB SSD storage space, plus a good secondary HDD

    • Network: At least 100 MB input/output Ethernet, preferably with redundant connections and HA switches

  2. MAP Quantity Your account needs to have at least 1,000,000 MAP.

Operating System Requirements

Atlas client supports mainstream operating systems - Linux, MacOS, Windows. This means you can run the node on a regular desktop or server and install the operating system that suits you best on these devices. To avoid potential issues and security vulnerabilities, make sure your operating system is up to date.

Software Requirements

Building Atlas requires git, Go (version 1.14 or higher), and a C compiler.

Clone the Code Repository and Build

git clone https://github.com/mapprotocol/atlas.git
cd atlas
git checkout v1.1.5
make atlas

Running the Node

Run atlas -h to get help information.

Running a Mainnet Node

atlas --datadir ./node console

Running a Single-Node Network

A single-node network is used for testing and development purposes. It does not sync with any other network and does not store any data.

To run a single-node network, run the following command:

atlas --datadir ./node --single console

If you add the --http flag in the command, it will enable the RPC server, and then you can access RPC via http://127.0.0.1:7445.

atlas --datadir ./node --single --http --http.addr "127.0.0.1" --http.port 7445 console
Previousdeploy atlasNextrun atlas(archive)

Last updated 1 year ago