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
  • What is the Marker
  • Building Marker
  • Commands
  • Optional: Run a Full Node

Was this helpful?

  1. Develop
  2. MAP Relay Chain

Marker

Introduction to the Map Command Line Interface and installation instructions.

What is the Marker

Marker contains tools to make genesis.json and some client commands to better link Map contracts.

The Command Line Interface allows users to interact with the Map Protocol smart contracts.

It allows you to interact with the Map Protocol and smart contracts using command-line tools rather than writing go Script. Some common features you may want to consider are helping users participate in elections or in on-chain governance, voting for validators, or helping users interact with multi-sig contracts.

Building Marker

Building `Marker` requires both a Go (version 1.14 or later) and a C compiler.You can install them using your favourite package manager.
git clone https://github.com/mapprotocol/atlas.git
cd atlas
make marker 

Now you can run "./build/bin/marker" to launch marker or switch to ./build/bin path and run "./marker" to launch marker

Commands

The tool is broken down into modules and commands with the following pattern:

./marker <command> <...args> 

The Marker tool assumes that users are running a node which they have access to signing transactions on.

Please note that our commands need to specify your keystore file, so you need to generate your keystore file in advance.

The method of generating keystore file is here:

  1. you need to building atlas project,building atlas requires both a Go (version 1.14 or later) and a C compiler.

  2. download our atlas project and use this command: git clone https://github.com/mapprotocol/atlas.git in your favorite folder.

  3. Switch to atlas project folder use this command go build -o ./favoritefolder/atlas *.go will generate atlas client in the directory specified by -o.

  4. Use your client generate your keystore file like this.

USAGE
 ./atlas account new --keystore "keystore path"
EXAMPLES:
 ./atlas account new --keystore ./datadir/keystore
RESPONSE:
Your new account is locked with a password. Please give a password. Do not forget this password.
Password:
Repeat password:

Your new key was generated

Public address of the key:   0x929510A8b54D3a8d7943e2Cdb5BA1888F7Ab7C4a
Path of the secret key file: ./datadir/keystore/UTC--2022-03-15T02-11-43.837807000Z--929510a8b54d3a8d7943e2cdb5ba1888f7ab7c4a
The keystore has been stored in the directory specified by --keystore.

If you already have an account,you can use the atlas client to convert. Enter the atlas console and use the command:

USAGE
./atlas --dataDir "./data" console
web3.personal.importRawKey("your private key","your password")
EXAMPLES:
> web3.personal.importRawKey("eaffcd749482e68ca4ccf5a07a52eb7ff876ea461fbab642b2b57bcb33edb280","linjing")
"0xd2f9e7716cc88944e5ed9f675649532c80d765f8"
The keystore has been stored in the directory specified by --dataDir.

Optional: Run a Full Node

Commands need to connect to a Map node to execute most functionality.

PreviousDeployNextGenesis

Last updated 1 year ago

Was this helpful?

We recommend using to create the keystore, export the private key, and use the private key to restore the keystore

ethkey