Proposal #8335

unfreeze · executed

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

Target TJiHEgg9SUcEKiqTpBw7idfJzH2CG5cPDS
Submitted2026-04-13 19:34 UTC
Executed2026-04-13 20:18 UTC
Interval44.0 min
Submit tx 75ea3f30d87f4b44ea139870d2b9d826db61b59b4a2789dd0622cb9452e90ca3
Execute tx 522bad475610f193e26396a73bc944c08fa15f33439b4664722d6f8622cd6a70

Where this interval sits

Longer than 52% of the 5,922 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-04-13 19:34 UTC · block 81,813,738
  2. unfreeze 2026-04-13 20:18 UTC · block 81,814,618
  3. executed 2026-04-13 20:18 UTC · block 81,814,618

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.