Building an application on a blockchain is a real challenge for developers who are seeking to leverage the power of the decentralized Web. With that in mind, dfuse is inviting experienced developers to share their journey of building these next-generation dapps. This week, we are glad to have Max Gravitt, Founder at Digital Scarcity and one of the early power users of the dfuse API.

Building an application on a blockchain is a real challenge for developers who are seeking to leverage the power of the decentralized Web. With that in mind, dfuse is inviting experienced developers to share their journey of building these next-generation dapps. To launch the series, we are pleased to speak with Kedar Iyer, Director Of Software Development at Everipedia and one of the early user of the dfuse API.

Until now, there has been no way to search through the entire transaction history on a public blockchain with the power of a modern search engine. Block explorers have been limited to looking up individual transactions or accounts by ID. But now, thanks to dfuse, the contents of a blockchain are easy to search.

The dfuse API is constantly evolving, with new features being added to help developers build faster for the blockchain. Today, there are endpoints available for the EOS mainnet, CryptoKylin and Jungle 2.0 test networks. We invite you to read the API documentation that we're constantly enriching.

We’d love to share new features we’ve been working on for eosq - the high-precision block explorer. Some are game changers for developing on EOS, yet some are subtle in the UI, or are shown only in certain transactions. We’d like to highlight them since they will make developing on EOS much easier.

There’s widespread excitement about the new Web 3.0 era of decentralized apps, but up to now most dapps have struggled to deliver really compelling user experiences. In general, dapp user experiences lag far behind what users have come to expect in the conventional Web 2.0 world.

There’s a deep underlying reason for this — dapp developers have lacked the powerful platforms and interfaces that are commonplace in Web 2.0 and that make it easy to deliver great user experiences.

One of the most used testnets for EOS was the Jungle Testnet. Recently, it relaunched as Jungle 2.0. dfuse is glad to join on to this new testnet, offering an API service to all developers who want to deploy and test on Jungle 2.0.

The goal of eosq, the high-precision block explorer built by the EOS Canada team, is to help developers find the key information they require from the blockchain. One of the main feats we first set out to tackle was the data pipeline on which eosq would rely, which was the genesis of the dfuse API for EOS.

Best of luck to you and your team over the course of these next sleepless hours while you develop your submission to the EOS San Fransisco Hackathon! We here at dfuse wanted to create a quick one-pager that will help you access a few tools that will make your life a little easier.

If you would like access to a streaming API that is connected to both the EOS mainnet and the CryptoKylin testnet, you can apply for your free API key in the form below.

New Code Releases

1. eosws-js new Javascript library, exposing new features
2. eosws-go new Golang library, exposing new features
3. dfuse API updated documentation, check the "Release Notes"
4. eosc improved to support headers to use push guaranteed endpoints.

Quick summary of new API features

1. New REST endpoint (/v0/state/table) to query the blockchain state at any block number
2. New instrumented REST proxy for /v1/chain/push_transaction, with stronger guarantees (block inclusion, irreversible attained) before returning
3. Support for tracking longest chain in `get_table_rows` (with undo and redo), giving a constantly syncing view of a given table
4. New message `get_transaction_lifecycle` that provides a complete view of a transaction's lifecycle, navigating its state changes through deferred creation, cancellation, and updating you as it changes.