Exploring Ethereum
Last updated
Was this helpful?
Last updated
Was this helpful?
Getting started with Substreams might feel challenging, but you are not alone! The Substreams Explorers are a set of projects, modules, and code samples that allow you to explore and discover the main features of Substreams.
Tip: This tutorial teaches you how to build a Substreams from scratch.
Remember that you can auto-generate a filtered Substreams module by using the .
The Ethereum block model for Substreams is represented by the Rust struct.
Before moving forward, make sure to reference the minimal path within the .
The https://github.com/streamingfast/substreams-explorers GitHub repository contains all the Substreams Explorers currently available. You can simply clone the repository:
You should be familiar with the basic Substreams terminology, which includes:
Modules (understanding the difference between a map and a store module)
Protobufs (understanding what they are)
The Ethereum Explorer consists of several Substreams modules showcasing the most basic operations that you can perform with Substreams on the Ethereum blockchain.
You can find the Ethereum Explorer at
The modules in this repository answer some interesting questions when developing a blockchain application:
For every block, the map_block_meta module retrieves the most relevant information of the block (number, hash, and parent hash).
Given any combination of two parameters (from and to), the map_filter_transactions filters a transaction among all transactions in the blockchain. This involves:
Providing the filters (only the from fields, only the to field, both from and to fields, or none)
Iterating over all the transactions.
Filtering the transactions, according to the parameters provided. For example, from == tx_from, from == tx_from and to == tx_to.
Given a smart contract address parameter (contract_address), the map_contract_events module retrieves all the events related to a specific smart contract. This involves:
Iterating over all the logs of a block.
Filtering the log, where the address field is equal to the smart contract address parameter (address == contract_address).
In the following sections, you will go through every module, run the corresponding Substreams, and understand every piece of code. Let's go!
The proto folder contains the Protobuf definitions for the transformations. In this example, there are three Protobuf objects, which are the outputs of the Substreams module mentioned in the previous section: BlockMeta (which represents the information of an Ethereum block), Transaction (which is an abstraction for an Ethereum transaction), and Event (an abstraction for an Ethereum event).
The src folder contains the source code of the Substreams transformations. Every module has its corresponding Rust file.
The substreams.yml is the Substreams manifest, which defines relevant information, such as the inputs/outputs of every module or the Protobuf files.
Let's take a closer look at the Substreams manifest (substreams.yml):
The protobuf section specifies the location of the Protobuf files used in the Substreams (i.e. where are the files defining the objects that you are going to use as output). In this example, the files are under the proto folder.
When you run Substreams, you are really executing a Rust application inside a WASM container. Therefore, Substreams needs to know where is the WASM executable. The binaries section specifies the location of the WASM executable.
You may find these additional resources helpful for developing your first Solana application.
Every module must be defined in the manifest, along with its kind, inputs and outputs. In this example, the map_block_meta module is a mapper that takes a raw Ethereum block as input () and outputs the BlockMeta protobuf. Basically, the map_block_meta module returns a reduced version of the Ethereum block.
The lets you explore all the tools available in the Substreams CLI.
The dives deeper into navigating the substreams.yaml.
