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

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

What changes in the staking engine when two networks have different block times?

Every economic quantity in the staking engine runs on seconds, so it is the same on any chain. Exactly one guard counts blocks, and its wall-clock length is the only thing that varies with the network.

Known formally as Whitepaper 2.4, section 25.9: clocks in the BlazePhoenix whitepaper.

BlazePhoenix Engineering · article updated 2026-11-16 · site dataset through 2026-11-19 · 6 min · written from the deployed bytecode

By Mitra (@Sigmacrit) — anonymous developer of the BlazePhoenix protocol. The code is the résumé.

Abstract in 15 languages · resumo · resumen · 摘要 · 要旨 · ملخص

English — 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.

Português — O motor de staking mantém a sua economia em segundos, que têm a mesma duração em todas as chains, e usa blocos para uma única coisa: a guarda MIN_DEPOSIT_BLOCKS, definida em 10, que impede que um depósito seja usado de imediato. Essa guarda é a única grandeza cuja duração em tempo real depende do tempo de bloco da rede.

Español — El motor de staking mantiene su economía en segundos, que duran lo mismo en todas las cadenas, y usa bloques para una sola cosa: la guardia MIN_DEPOSIT_BLOCKS, fijada en 10, que impide usar un depósito de inmediato. Esa guardia es la única magnitud cuya duración en tiempo real depende del tiempo de bloque de la red.

Français — Le moteur de staking tient son économie en secondes, qui durent autant sur toutes les chaînes, et n'utilise les blocs que pour une seule chose : la garde MIN_DEPOSIT_BLOCKS, fixée à 10, qui empêche d'utiliser un dépôt tout de suite. Cette garde est la seule grandeur dont la durée réelle dépend du temps de bloc du réseau.

Deutsch — Die Staking-Engine führt ihre Ökonomie in Sekunden, die auf jeder Chain gleich lang sind, und nutzt Blöcke nur für eine einzige Sache: den Guard MIN_DEPOSIT_BLOCKS, auf 10 gesetzt, der verhindert, dass eine Einzahlung sofort verwendet wird. Dieser Guard ist die einzige Größe, deren Echtzeitdauer von der Blockzeit des Netzwerks abhängt.

Русский — Движок стейкинга держит свою экономику в секундах, которые одинаковы по длине в любой сети, а блоки использует только для одного: гарда MIN_DEPOSIT_BLOCKS, равная 10, не даёт использовать депозит сразу. Эта гарда — единственная величина, чья длительность в реальном времени зависит от времени блока сети.

Türkçe — Staking motoru ekonomisini her zincirde aynı uzunlukta olan saniyelerle tutar ve blokları yalnızca tek bir iş için kullanır: 10 olarak ayarlanmış MIN_DEPOSIT_BLOCKS koruması, bir mevduatın hemen kullanılmasını engeller. Gerçek zamanlı süresi ağın blok süresine bağlı olan tek nicelik bu korumadır.

العربية — يُبقي محرك الستيكنغ اقتصاده بالثواني، وهي متساوية الطول على كل سلسلة، ولا يستخدم الكتل إلا لشيء واحد: حارس MIN_DEPOSIT_BLOCKS المضبوط على 10، الذي يمنع استخدام الإيداع فورًا. هذا الحارس هو الكمية الوحيدة التي تتوقف مدتها الفعلية على زمن كتلة الشبكة.

हिन्दी — स्टेकिंग इंजन अपना अर्थशास्त्र सेकंड में रखता है, जो हर चेन पर बराबर लंबाई के होते हैं, और ब्लॉक का उपयोग केवल एक काम के लिए करता है: MIN_DEPOSIT_BLOCKS गार्ड, जिसका मान 10 है, जो किसी डिपॉज़िट को तुरंत इस्तेमाल होने से रोकता है। यही गार्ड एकमात्र राशि है जिसकी वास्तविक समय-अवधि नेटवर्क के ब्लॉक टाइम पर निर्भर करती है।

日本語 — ステーキングエンジンは経済の計算を、どのチェーンでも同じ長さの秒で行い、ブロックを使うのはただ一つ、デポジットをすぐに使えなくする 10 に設定された MIN_DEPOSIT_BLOCKS ガードだけです。実時間の長さがネットワークのブロックタイムに左右される量は、このガードだけです。

中文 — 质押引擎的经济计算全部以秒为单位,而秒在每条链上长度相同,区块只用于一件事:设为 10 的 MIN_DEPOSIT_BLOCKS 守卫,它阻止存款被立即使用。这个守卫是唯一一个实际时长取决于网络出块时间的量。

한국어 — 스테이킹 엔진은 경제 계산을 모든 체인에서 길이가 같은 초 단위로 유지하고, 블록은 단 한 가지에만 씁니다. 예치금이 곧바로 쓰이지 못하게 하는, 10으로 설정된 MIN_DEPOSIT_BLOCKS 가드입니다. 실제 시간 길이가 네트워크 블록 타임에 좌우되는 양은 이 가드뿐입니다.

Bahasa Indonesia — Mesin staking menjaga ekonominya dalam detik, yang sama panjangnya di setiap chain, dan memakai blok hanya untuk satu hal: guard MIN_DEPOSIT_BLOCKS, diatur ke 10, yang mencegah deposit langsung dipakai. Guard itu adalah satu-satunya besaran yang durasi waktu nyatanya bergantung pada waktu blok jaringan.

বাংলা — স্টেকিং ইঞ্জিন তার অর্থনীতি সেকেন্ডে রাখে, যা প্রতিটি চেইনে সমান দৈর্ঘ্যের, এবং ব্লক ব্যবহার করে মাত্র একটি কাজে: 10 নির্ধারিত MIN_DEPOSIT_BLOCKS গার্ড, যা ডিপোজিট সঙ্গে সঙ্গে ব্যবহার হতে দেয় না। যে একমাত্র রাশির বাস্তব সময়ের দৈর্ঘ্য নেটওয়ার্কের ব্লক টাইমের ওপর নির্ভর করে, সেটি এই গার্ড।

Filipino — Pinapanatili ng staking engine ang ekonomiya nito sa mga segundo, na pareho ang haba sa bawat chain, at gumagamit ng mga block para sa isang bagay lamang: ang MIN_DEPOSIT_BLOCKS guard, na nakatakda sa 10, na pumipigil sa deposit na magamit agad. Ang guard na iyon ang tanging dami na ang haba sa totoong oras ay nakadepende sa block time ng network.

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.

QuantityConstantUnitValue
Emission periodHALVING_PERIODseconds2 x 365 days = 63,072,000 s
Emission lengthEMISSION_LENGTHseconds4 periods = 252,288,000 s (8 years)
Lock boundsMIN_LOCK_DAYS, MAX_LOCK_DAYSdays90 and 2,555
Deposit age guardMIN_DEPOSIT_BLOCKSblocks10
Emergency graceEMERGENCY_GRACE_PERIODseconds30 days
Maintenance gapMAINT_GAP_UNITseconds15 minutes

Source: Whitepaper 2.4, section 25.9 (staking repository at commit c0366cf).

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.

  1. Read `HALVING_PERIOD` and `EMISSION_LENGTH` from the contract: both are seconds.
  2. Confirm that the emission length is exactly four periods.
  3. Read `MIN_DEPOSIT_BLOCKS` in the source (it is a private constant, so there is no getter): it is the only constant counted in blocks.
  4. Once both deployments exist, compare them: every constant is the same, and only the wall-clock time of ten blocks differs.

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.

Do not trust this page — reproduce it

Every claim above is checkable against the chain. Start here:

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.
Cite this article

Licensed CC BY-NC-ND 4.0: quote and cite it with attribution and a link. Commercial use and derivative versions need written permission from BlazePhoenix; translations are made by BlazePhoenix. Copy a ready-made citation:

BlazePhoenix (2026). One clock per chain: seconds, blocks and a schedule that does not drift. BlazePhoenix Engineering. https://blazephoenix.xyz/learn/one-clock-per-chain/
@misc{blazephoenix_one_clock_per_chain,
  title  = {One clock per chain: seconds, blocks and a schedule that does not drift},
  author = {BlazePhoenix},
  year   = {2026},
  url    = {https://blazephoenix.xyz/learn/one-clock-per-chain/},
  note   = {Accessed: reproduce the claim with the command above}
}

Writing an answer, a wiki entry or a paper? The claim above is reproducible against the chain before you quote it — which is the only sound basis for citing a technical source at all.

Contracts are verified on every chain we deploy to — addresses in the protocol manifest. Deeper formal treatment: the whitepaper (PDF).

Related engineering

Next in Architecture · 8 / 20
Two deployments, one schedule each: staking on Base and Robinhood Chain ›The staking engine is two independent contracts, one on Base and one on Robinhood Chain, each with its own 90,000,000 BZPX reserve and its own clock. The 180,000,000 total is a sum of two budgets, not one pool.6 min

Questions, a partnership or a bug to report? Contact us or email contact@blazephoenix.xyz

Go to APP