dfuse for EOSIO
All dfuse.io services for EOSIO, running from your laptop or from a container, released as a single statically linked binary:
See the general dfuse repository for other blockchain protocols implementations.
If it's the first time you boot a
nodeosnode, please review https://developers.eos.io/welcome/latest/tutorials/bios-boot-sequence and make sure you get a grasp of what this blockchain node is capable.
The default settings of
dfuseeosallow you to quickly bootstrap a working development chain by also managing the block producing node for you.
Build requirements: *
Go1.14 or higher (installation) *
yarn1.15 or higher (installation)
This will install the binary in your
$HOME/go/bin). Make sure this folder is in your
PATHenv variable. If it's missing, take a look at TROUBLESHOOTING.md.
Note -- If you're getting yarn dependency warnings while running the
yarn install && yarn buildcommands above, you can normally safely ignore those and move forward with the installation. If you're getting an error while installing and/or compiling, see TROUBLESHOOTING.md.
Initialize a few configuration files in your working directory (
y(yes) when being prompted for
Do you want dfuse for EOSIO to run a producing node for you?. If you intend is to sync an existing chain, follow Syncing an existing chain with
Optionally, you can also copy over a boot sequence to have dfuse bootstraps your chain with accounts + system contracts to have a chain ready for development in a matter of seconds:
wget -O bootseq.yaml https://raw.githubusercontent.com/dfuse-io/dfuse-eosio/develop/devel/standard/bootseq.yaml
When you're ready, boot your instance with:
A successful start will list the launching applications as well as the graphical interfaces with their relevant links:
In this mode, two nodeos instances will now be running on your machine, a block producer node and a mindreader node, and the dfuse services should be ready in a couple seconds.
If you chose to sync to an existing chain, only the mindreader node will launch. It may take a while for the initial sync depending on the size of the chain and the services may generate various error logs until it catches up (more options for quickly syncing with an existing chain will be proposed in upcoming releases).
The EOSIO-specific services: * abicodec: ABI encoding and decoding service * statedb: The dfuse State database for EOSIO, with all tables at any block height * kvdb-loader: Service that loads data into the
kvdbstorage * dashboard: Server and UI for the dfuse for EOSIO dashboard. * eosq: The famous https://eosq.app block explorer * eosws: The REST, Websocket service, push guarantee, chain pass-through service.
dfuse Products's EOSIO-specific hooks and plugins: * search plugin, object mappers, EOSIO-specific indexer, results mapper (along with the search client. * dgraphql resolvers, with all data schemas for EOSIO * blockmeta plugin, for EOS-specific