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.

We have released some new changes - some breaking changes (all clearly documented - mainly renames), new libraries, and some new features.

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.

NOTE: this is a BETA release. Please join the discussion in the dfuse API Telegram channel if you have any questions or feature requests.