Developers who write smart contracts, or seek to integrate EOSIO blockchain data into their application, require a testing ground in which to deploy, iterate and debug. Recently, dfuse began supporting developers who were seeking to utilize Block.one’s official EOSIO Testnet, and now we are excited to endorse it as our preferred testnet.
Ever since the release of our open source single binary "dfuse for EOSIO", we have received many requests to explain the foundational architecture that it encompasses. In this video, Alex explains the genesis, the features, and the power of pitreos, our open-source backup and recovery tool for nodeos. Learn why we custom built this incredibly fast tool, and how you can take advantage of it.
Ever since the release of our open source single binary "dfuse for EOSIO", we have received many requests to explain the foundational architecture that it encompasses. In this video, Alex continues his review of bstream - the block stream which is the low-level component of dfuse where all information passes through protobuf definitions to build dfuse block objects to be consumed.
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!
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.
EOSIO blockchains utilize Delegated Proof of Stake (DPoS) to determine who the network's validators will be at any given moment. To understand how the votes cast by the user base are calculated over time, we are going to look at the algorithms that underpin how vote strength is calculated on an EOSIO blockchain.
Often, calling a smart contract will cause it to call one or more methods within other smart contracts, creating internal transactions. While Ethereum is inherently structured this way, its native API doesn't expose this information in an easy-to-consume way. However, dfuse indexes these internal transactions, making them easily searchable and usable by your application.
Different factors can lead to a microfork, and it's important to ensure that your application can handle these chain reorganizations as they happen. Alex explains what a microfork is, as well as when and why one would occur. Developers who utilize dfuse can have updates about microforks sent to them in real time, ensuring the most up-to-date information is being fed into their application.
Be sure to check out these other resources to further understand how dfuse solves this challenge for you:
Ever since the release of our open source single binary "dfuse for EOSIO", we have received many requests to explain the foundational architecture that it encompasses. In this video, Alex reviews bstream - the block stream which is the low-level component of dfuse where all information passes through protobuf definitions to build dfuse block objects to be consumed.
Between a transaction being pushed to the Ethereum blockchain, and then being considered “trustworthy”, there are many different transitions that it can pass through. Dennis Liu demonstrates how subscribing to dfuse’s Ethereum Lifecycle-enabled endpoints can greatly empower the user experience that your application can deliver.
