Operator hub

How blocks are built

devnet · next · development

Last updated 2026-08-19

How blocks are built

The block

Blocks arrive on a one-second average cadence, with a roadmap toward sub-millisecond settlement. Each block bundles proof hashes from completed inference sessions, up to a 2 MB block size limit.

Validators do the building. A validator takes the proofs miners submit, includes each proof's hash in a block, and the session settles.

The data-availability layer

Validators also store the model weights that agents and miners rely on, in the data-availability layer, so sessions can be served.

The same layer holds the audit evidence for the challenge window, under serve-or-slash — see the challenge game.

Who is in the set

The validator set is capped at 1,000. Roughly 50 rotate each month: the worst-performing 50 are replaced by the top 50 in waiting, on availability and uptime.

What validators earn

The active set shares 10% of block rewards. Live transaction fees currently burn 10% and route the remainder to the block author; that routing is interim.

Status

Draft whitepaper. Live transaction-fee routing remains interim.