Proposal #10672

freeze · executed

The multisig announced this 53.2 min before it took effect. That interval is the only warning anyone got.

Target TXfpYiGyZS8CEnxJYJRCvSfAY6z7Wkb776
Submitted2026-09-03 15:23 UTC
Executed2026-09-03 16:16 UTC
Interval53.2 min
Submit tx e9355d1f5f0588adae8eaa528bb3bdc1144ce77583bd43edbcb68e478ddc1e39
Execute tx 8d49663268b08bbb69b4826b29d7e1386363bd7780c5fd8d08442f550564ed86

Where this interval sits

Longer than 56% of the 5,894 executed freezes we hold.

Measured against executed proposals only. Counting the abandoned ones would push every percentile toward 100% and make a long wait read as “about to happen”, which is backwards.

Issued alone. No other proposal within ten minutes either side.

What happened on chain

  1. proposal 2026-09-03 15:23 UTC · block 85,925,769
  2. freeze 2026-09-03 16:16 UTC · block 85,926,834
  3. executed 2026-09-03 16:16 UTC · block 85,926,834

State events are matched to this proposal by target address and proximity in time. The chain carries no field binding the two, so this pairing is inference — stated plainly rather than presented as proof.

Watch this address

This page is one proposal. The bot tells you the next one, on this address, the second it is submitted.

Watch in Telegram

↑↓ move ↵ open ↵ look it up esc close Nothing you type here is stored or sent anywhere but this lookup.