Integrating 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.

Integration using EVM Endpoints

Running an ABEY Chain node

you can get it from source code or release versin.

from source code:

// make sure the golang env

git clone
cd go-abey
git checkout release3.0
make gabey

than start a node with the RPC service on the background,use gabey -h get more details.

./build/bin/gabey --datadir ./data --gcmode "archive" --syncmode "full" --rpc --rpcaddr ""  --rpccorsdomain "*" --rpcvhosts "*"  --rpcapi "eth,abey,web3,net,impawn" console 

Interacting with the ABEY Chain

Interacting with the ABEYChain is identical to interacting with go-ethereum. You can find the reference material for ABEY API here.

Please note that personal_ namespace is turned off by default. To turn it on, you need to pass the appropriate command line .

Java SDK and Web3.js

you can use the Java SDK and web3.js libs interacting with the ABEYChain.

If you plan on extracting data from the ABEYChain into your own systems using golang, we recommend using our custom abeyclient.

Constructing transactions

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,Truffle and 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.

Last updated