Getting your application to a production-ready stage is no easy feat. It takes many rounds of iteration, improvements, and bug fixes. For this, a private testnet is a blockchain developer’s best friend. We wanted to touch upon some of the reasons that a dfuse-enabled testnet is the key to saving development time, money, and frustration. It also happens that we offer a free dfuse account for testnets, what a coincidence!

Spin Up and Tear Down With Ease

When we set out to release the open-source binary dfuse for EOSIO, one must-have was that a developer must be able to easily create > wipe clean > restart a chain, each with just a single command. With dfuseeos start and dfuseeos purge, we have provided exactly that. With only 14 keystrokes, you can spin up a powerful and private testnet at will, and restart as you need.

Fully Feature Enabled

Working on debugging your smart contract? Utilize our console log reader. Need to find which actions caused a change in a smart contract’s database? Utilize our sophisticated search query language. Need a block explorer to easily review historical actions on-chain? Easily access your private eosq instance and GraphiQL playground on port 8080 — comes pre-packaged with dfuse for EOSIO. These are but just a small sampling of the many features you’ll have access to.

Develop Your Application In Stealth

With the public and accessible nature of blockchain, many development teams enjoy having the ability to develop their contract locally without anyone being able to see their tests. And since dfuse supports public testnets as well, once you are ready to test your smart contract on a test chain with thousands of other accounts and many concurrent actions passing through the network, you’ll be able to migrate with ease. We suggest moving to the EOSIO Testnet hosted by

Avoid Adverse Network Conditions

When working on a public testnet, you are exposed to various network conditions. While these may be good for testing purposes at one point in the development cycle, they may greatly hinder your ability to advance through other stages. Some things we’ve experienced in the past on public testnets were:

  • Many of the producing nodes being down simultaneously, thus causing the last irreversible block to stall for many hours
  • Throughput testing being performed by the network operators, bringing the testnet to a halt for all developers for hours at a time
  • Insufficient API access for your own testing needs
  • Broken token faucets, cutting off access to tokens when you need them
  • Poor peering between validating nodes, leading to frequent dropped blocks

These issues, among others, lead to wasted engineering time.


Integrate blockchain into your development stack is easier than ever. Download and start playing our open-source blockchain platform today, and when you’re ready, create your free dfuse account to develop on a public testnet. Let us know what you’re building and how we can help by joining us on Telegram and Twitter.