Bullet proof recipe for exchange use case scenario
We need to support exchanges, so bullet proof recipe is needed. (Actually, bullet is wrong word as it's not the bullets we usually struggle with).
-
CI/CD testing for deployment of exchange node -
Update README.md -
Update docs/exchangequickstart.md -
Update docs/example_config.ini
Some notes abut the exchange use case:
Consensus node with account history capabilities is required, however, it needs to track only the accounts that are used by the exchange, so that it will almost the same size as a regular consensus node.
It's good to have all the accounts that exchanges use in a common config.ini
file (see docs/example_config.ini) so we could enable minimal deployment time if given exchange opt-in for such feature, then we will be ready.
Exchange will use one of predefined tracked accounts, and/or add their set of desired tracked accounts via the command line (that's passed to hived inside the docker container).
Such deployed node need to listen on the localhost for websocket connections (for cli_wallet
purposes) and http in case of REST scripting is being used.
Fastest way to obtain a node is to deploy docker image for exchanges, that will optionally download block_log file or re-use local one and/or download most recent snapshot and load it.