Exchange Docking Reference

Data synchronization and storage

Use the node’s RPC interface to synchronize blocks and transactions, then save all the received information. This process requires dealing with temporary fork blocks - if the blocks acquired by the height can't be connected with the local stored best chain, the highest local block should be regained until they're connected. The original block with the same height will be discarded.

Recharge

To prevent the issue of temporary forking, it's recommended that more than 16 confirmations be considered as available transactions.

Coin Withdraw

The exchange maintains the UTXO set of every address to generate the currency transaction. The withdrawal transaction can be generated by the transaction utility.

Reference

ELA Node

https://github.com/elastos/Elastos.ELA

Main net config file

https://github.com/elastos/Elastos.ELA/blob/master/docs/mainnet_config.json.sample

Please put this file in the directory of ELA node and change the file name to config.json.

Test net config file

https://github.com/elastos/Elastos.ELA/blob/master/docs/testnet_config.json.sample

Please put this file in the directory of ELA node and change the file name to config.json.

RPC-API

https://api.elastos.io/ela https://api.trinity-tech.io/ela

Transaction utility

https://github.com/elastos/Elastos.ELA.Utilities.Java

Make and sign a transaction

RPC interface

https://github.com/elastos/Elastos.ELA/blob/master/docs/jsonrpc_apis.md

Get blocks and transactions

Send raw transactions

ELA client

https://github.com/elastos/Elastos.ELA/blob/master/docs/cli_user_guide.md

This is a command-line tool. Used for testing.

ELA Locking transaction recognition

https://github.com/elastos/Elastos.ELA/blob/master/docs/Locking_transaction_recognition.md

In case of a recharge, UTXO can't be spent