Integrate with an Exchange
The objective of this document is to provide a brief overview of how to integrate with the EVM-Compatible ABEY Chain. For teams that already support ETH, supporting the ABEY is as straightforward as spinning up an ABEY Chain node (which has the same API as go-ethereum) and populating ABEY Chain ChainID (179) when constructing transactions.
from source code:
// make sure the golang env
git clone https://github.com/abeychain/go-abey.git
git checkout release3.0
than start a node with the RPC service on the background,use
gabey -hget more details.
./build/bin/gabey --datadir ./data --gcmode "archive" --syncmode "full" --rpc --rpcaddr "0.0.0.0" --rpccorsdomain "*" --rpcvhosts "*" --rpcapi "eth,abey,web3,net,impawn" console
Please note that personal_ namespace is turned off by default. To turn it on, you need to pass the appropriate command line .
ABEYChain transactions are identical to standard EVM transactions with one exceptions::
They must be signed with ABEYChain’s ChainID (179).
For development purposes, ABEYChain 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.
ps: ABEYChain 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.