As more developers begin to incorporate dfuse for EOSIO into their development stack, we’ve received great feedback on improvements and additional features. Here’s a brief overview of some of things that can be found in the latest release, with a full technical detailing found here in the release log.
As we’re constantly working on improving the user experience with each release, be sure to “watch” the repository’s Releases page. Don’t be shy to let us know what your needs are, and any part of the experience that you feel can be improved, by opening an issue.
Public API Changes
eoswstransaction lifecycle fields
cancelation_irreversiblewere renamed to
System Administration Changes
On the System Administration side, meant for developers running a local version of the dfuse for EOSIO, we introduced many changes, some of them BREAKING.
Let’s begin with two new applications that have been added;
mindreader-stdin-- For those of you who already have a custom setup for managing
nodeos, this allows you to seed dfuse with the files it needs while keeping the setup you’ve been running on.
booter-- Booting up a chain with contracts and accounts already setup has never been easier. Craft your boot sequence to match your needs and run a simple command and in moments you’ve got your complete testing environment waiting to go.
We’ve also added 4 new commands to the
dfuseeos tools section, so be sure to get familiar with them and their subcommands to get the most out of your dfuse experience. This is in addition to the many flags we’ve added based on your incredible feedback thus far.
There have also been a number of naming changes that were incorporated into this release, most notably renaming
trxdb for the storage location of blocks and transactions. Also, the default amount of snapshots that dfuse will store before overwriting has been changed to
0 (for unlimited), rather than the last 5 snapshots.
This is but a small subset of the changes and improvements that have been introduced. Be sure to read through the full release notes to keep your tooling and monitoring up to date, as well as to take full advantage of the community feedback that we’ve incorporated. Again, please don’t be shy to let us know what you’d like to see in future releases of dfuse!