The Filecoin network uses the idea of tipsets to manage blocks within the blockchain. This page details what a tipset is, how they differ to blocks in other blockchains, and how developers should deal with tipsets.

The Filecoin network produces multiple blocks at every epoch. In simple terms, block producers run a local function that uses their quality-adjusted power, as represented in the power table, and randomness from the Drand network to determine if they’re eligible to produce a block for the current epoch. This consensus protocol is called expected consensus.

These blocks are assembled in a tipset, and the execution of their messages is deferred to the next tipset. Theoretically, there can be 0 to infinite blocks in a tipset. In practice, however, we see 5 to 10 blocks per tipset.

Wherever you see the term block in the Ethereum JSON-RPC, you should mentally read tipset. Before FEVM and the Filecoin Ethereum JSON-RPC, there was no single hash referring to a tipset. A tipset ID was the concatenation of block CIDs, which led to a variable length ID, and a pretty poor experience.

With the Ethereum JSON-RPC, we introduced the concept of the tipset CID for the first time! It is calculated by hashing the former tipset key using a blake-256 hash. Therefore:

  • Wherever you see block hash, think tipset hash.
  • Wherever you see block height, think tipset epoch.
  • Wherever you see block messages, think messages in all blocks in a tipset, in their order of appearance, deduplicated and returned in canonical order of execution.