# One clock per chain: seconds, blocks and a schedule that does not drift

> Canonical: https://blazephoenix.xyz/learn/one-clock-per-chain/
> License: CC BY-NC-ND 4.0 (attribution + link) · © 2026 BlazePhoenix
> Updated: 2026-11-16

The staking engine keeps its economics in seconds, which are the same length on every chain, and uses blocks for exactly one thing: the MIN_DEPOSIT_BLOCKS guard, set to 10, that stops a deposit from being used straight away. That guard is the only quantity whose wall-clock length depends on the network block time.

Short answer: almost nothing. The staking contract keeps its economics in seconds, and a second is the same length on every chain. It uses blocks for exactly one thing, the guard that stops a deposit from being used in the same transaction or the same few blocks. That guard is the only quantity whose wall-clock length depends on the network's block time.

This matters because the staking engine is deployed twice, once per network, and each deployment is independent (see the article on the two deployments). If the schedule were counted in blocks, two chains would run two different programmes from the same code.

## Which quantity uses which unit

The whitepaper (section 25.9) sorts the contract's time into two units. Seconds, read from `block.timestamp`, drive the emission schedule, the interest index, the lock and its expiry, the emergency timestamp and the maintenance gap. Blocks, read from `block.number`, drive one guard only: `MIN_DEPOSIT_BLOCKS`, set to 10.

## What the block guard does

A deposit must age more than ten blocks before `withdraw`, `claimPureYield`, `lock` or a debt-free reset can act on it. The purpose is structural: value that arrives and leaves inside one transaction, or within a few blocks of it, cannot capture the schedule.

Ten blocks is a count, not a duration. How long ten blocks last on a given network depends on that network's block time, and the paper does not assert a figure. What the guard gives you is the same rule on every chain; what differs is the time it takes to elapse.

## Why the schedule counts in seconds

The emission closed form reads elapsed seconds since `emissionStart`, so a deployment on any chain emits the same amount in the same number of seconds. A period is 2 x 365 days, not two calendar years: leap days are not counted, so 'eight years' in the paper means 8 x 365 = 2,920 days.

The same rule governs a halt. When emergency mode is entered, the interest index and the emission clock freeze. `cancelEmergency` slides both clocks to the current time, so the halt is never charged or emitted retroactively.

## What this does not claim

It does not state how many seconds ten blocks take on either network. It does not say the guard is a security boundary on its own: it is one of several gates described in the entry-point table of section 25.2. And it describes the staking engine as designed in the repository, which is pre-launch: the site gives its launch as Q2 2027.

**Verify it yourself:** In a checkout of the staking repository at commit c0366cf, read the constants HALVING_PERIOD, EMISSION_LENGTH and MIN_DEPOSIT_BLOCKS in src/BlazePhoenixStaking.sol (declared near the emission and lock constants) and confirm that the first two are expressed in seconds and the third in blocks. Reading: section 25.9 of the 2.4 whitepaper.

Related: https://blazephoenix.xyz/learn/invariants-and-time/ · https://blazephoenix.xyz/learn/the-halving-schedule/ · https://blazephoenix.xyz/learn/two-staking-deployments/
