Validators

Retium separates transaction validation from block finality. When a transaction enters the network, it is routed directly into an open block instead of waiting in a mempool. The Matchmaker assigns five Workers to check the transaction. If at least three Workers approve it, the transaction reaches transaction-level finality.

Blocks are sealed on a fixed cycle, not only when they are full. This keeps the network rhythm predictable, even during low or uneven traffic.

After a block is sealed, the Keeper layer checks it through deterministic consensus. Keepers independently recompute the same mathematical result from the same inputs. When a majority of Keepers agree, the block has reached cryptographic consensus.

Suits act as finality coordinators. Five independent Suits are assigned to each sealed block, and they coordinate block finality by watching for Keeper agreement. Once the required Keeper consensus is reached, a Suit broadcasts the finality verdict and the block becomes HardFinal.

Keepers also manage the tick cycle, which controls the broader rhythm of block production. Each tick represents a new phase of mesh growth, and the network advances only after the current phase is finalized.

The Matchmaker keeps assignments dynamic and unpredictable, so validators do not know in advance which transaction or block they will handle. This helps prevent coordination and keeps validation independent.