Timelord Status
Network health for the time half of Proof of Space and Time. This is deliberately a status board, not a leaderboard: VDF proofs carry no identity, so there is no honest way to attribute an infusion to a particular operator, and inventing one would be fiction.
Chain advancing
YES
last block 42s ago
Blocks last hour
177
92.2% of the ~192 expected
Observed block time
18.68s
target 18.75s
Sub-slot iters
69,206,016
VDF work per sub-slot
Timelord Operations Fund
JSON- Per block
- 0.0005 STK (0.1% of the block reward)
- Accrued on chain
- 124.9365 STK
- Expected at height 250,071
- 125.0355 STK
- Current balance
- 124.9365 STK
- Fund address
- tstk1kv02yzr83w0qc7d33rrqm057tjr4y8st83g3tcqmf6229frc7wvs5z0ugk
The fund accrues 0.0005 STK × every block since height 1, enforced by consensus.
Accrued sits at or just below the expected figure because the newest blocks' rewards are claimed
on the next transaction block.
Infusion cadence, last 24 hours
Blocks per hour is the visible output of timelord infusions. A healthy chain at the design
target produces about 192 blocks an hour; a young
testnet whose difficulty has not settled will sit above or below that.
Why there is no per-timelord ranking. Green Stack mints the 0.1% timelord share to a
single fixed, rotatable multisig-controlled fund address — exactly like the founder reward — and
distributes it to operators off-chain, outside consensus. That is a deliberate design decision: the
upstream VDF proof format carries no operator identity field, and Green Stack chose not to fork the
Rust VDF layer to add one. With no identity in the proof, any explorer that claims to rank individual
timelords is guessing.