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.
Block.one has developed a highly performant blockchain platform, capable of handling a high number of write operations per second for a distributed system. With all of this data, there was a need for an equally performant method to read this data. This is where we focused our attention.
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 manageos - the dfuse node manager - which wraps nodeos and adds functionality through many additional endpoints. He also introduces our mindreader service, for offering block logs over gRPC.
To make the resources on an EOSIO network more easily available to developers who need them, Block.one wrote the Resource Exchange (REX) smart contract. While there are many great tutorials demonstrating how to use REX, a developer still needs to understand the underlying code. Here's our technical guide to understanding REX.
As Ultra gets closer to its public launch, they need to ensure that their platform is performant and ready for scale. Sometimes it makes the most sense to partner with best-of-breed solutions that are already in the market, so that Ultra can focus on their core capabilities. Ultra gains the experience of their external partners, while freeing up resources to focus on improving core competencies.
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 explores the deepmind instrumentation used to exfiltrate data from nodeos, as well as the dfuse data model and the protobuf package it uses.
