Integrate an Exchange
The objective of this document is to provide a brief overview of how to integrate with the EVM-Compatible MAP Relay Chain. For teams that already support ETH, supporting the MAP Relay Chain is as straightforward as spinning up an MAP Relay Chain node (atlas) (which has the same API as go-ethereum) and populating MAP Relay Chain ID (22776) when constructing transactions.
from source code:
// make sure the golang env
git clone https://github.com/mapprotocol/atlas.git
git checkout release_v1
then start a node with the RPC service on the background,use
./build/bin/atlas -hget more details.
./build/bin/atlas --datadir ./data --gcmode "archive" --syncmode "full" --port 28360 --v5disc --http --http.addr "0.0.0.0" --http.api eth,web3,net,debug,txpool,header,istanbul --http.corsdomain "*" --http.vhosts "*"
Interacting with the Atlas node is identical to interacting with go-ethereum. You can find the reference material for Atlas API here.
Please note that personal_ namespace is turned off by default. To turn it on, you need to pass the appropriate command line .
If you plan on extracting data from the Atlas into your own systems using golang, we recommend using our custom ethclient.
MAP Relay chain transactions are identical to standard EVM transactions with one exceptions::
They must be signed with MAP Relay Chain ChainID (22776).
For development purposes, MAP Relay Chain supports all the popular tooling for Ethereum,like as
MetaMask and Remix,
Hardhat, so developers familiar with Ethereum and Solidity can feel right at home.
We are compatible with the improvement of Ethereum eip1559, and set the minimum base fee to 100GWei.
ps: MAP Relay Chain consensus provides fast and irreversible finality with 5 seconds. To query the most up-to-date finalized block, query any value (i.e. block, balance, state, etc.) with the latest parameter.