Provides DAC specific api endpoints for use by the eosdac-client.
- RabbitMQ (Install)
- Available State History node
- MongoDB
- NodeJS v12
The eosdac-api consists of 4 components
This reads from the state history node and can be run in parallel to process many streams during replay. The filler listens for interested contracts specified in the config file and if detected, the transaction is put into a queue for later processing from the binary.
It only processes enough of a given transaction instead of deserialising all of the payload to save cpu cycles.
When the filler is started with the -r flag, it will split the replay range into many block ranges and put them on the queue.
This process monitors this queue and pulls a range of blocks from the state history.
The processor reads interested jobs from the queue and extracts the data for indexing in mongodb.
The processor will also trigger any registered watchers after processing a state delta or action receipt.
The API service uses fastify to provide a fast API development platform, it reads data from mongodb.
Once running the api will open the configured port and provide document on http://your.domain/v1/eosdac/docs
git clone [email protected]:Alien-Worlds/eosdac-contracts.git
cd eosdac-contracts
yarn
yarn test
The command yarn test will build and start a docker container with a fresh blockchain, compile and deploy the eosdac-contracts and run the tests. The docker container will stay running and the nodeos API node of the blockchain will be exposed on port 8888. You can verify that the blockchain is running from the host system:
curl http://127.0.0.1:8888/v1/chain/get_info
It also creates a docker network named lamington that you can use to connect to the blockchain from other docker containers.
Each config is named [name].config.js, copy example.config.js to your name of choice, eg. cp example.config.js jungle.config.js
Edit your file to include the correct contract names and endpoints. amq.connectionString is your your RabbitMQ connection string.
In order to start the services in docker, just use the command:
CONFIG=example docker compose up --build
You can switch between different configs by giving a different value to the CONFIG env variable.
If you use the default example config, it will automatically try to connect to a blockchain running locally on port 8888. In order to run it, see above.
If you are deploying the api after your contracts have been deployed or you need to refill your database, run the filler directly using the -r flag:
CONFIG=jungle ./eosdac-filler.js -r
You can also use the -s flag to specify a replay with a start block (so you don't have to start from block 0):
CONFIG=jungle ./eosdac-filler.js -r -s 25629516
Replays will spawn a number of processes to pull blocks from the chain, if you want to run more filler processes on another machine, you can start with the blockrange process using pm2 (it should be started automatically).
pm2 start --only eosdac-blockrange-jungle
The eosdac-ws process opens a websocket which can be used by external clients to listen for messages about significant events.
Connect to the websocket server, eosDAC provides endpoints at the following locations:
ws://api.eosdac.io:3030- EOS Mainnetws://api-jungle.eosdac.io:3030- Jungle Network
This example will connect and request notifications for a particular DAC ID
const endpoint = 'ws://api.eosdac.io:3030';
const dac_id = 'eosdac';
const ws = new WebSocket(endpoint);
ws.onmessage = (msg) => {
console.log('Received message', msg.data);
};
ws.onopen = () => {
console.log(`Websocket opened to ${endpoint}`);
ws.send(JSON.stringify({type:'register', data:{dac_id}}));
console.log(`Sent register message for ${dac_id}`);
};
The following notifications are sent
MSIG_PROPOSED
MSIG_APPROVED
MSIG_UNAPPROVED
MSIG_CANCELLED
MSIG_EXECUTED
VOTES_CHANGED
NEW_PERIOD