Proposal #6008

freeze · executed

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

Target TVBf9EG6zPnUar4ArkfvYi3oLiCGtztCBf
Submitted2025-10-08 19:41 UTC
Executed2025-10-08 20:04 UTC
Interval22.8 min
Submit tx f569c474a93ec3d2a04b49cf9b72c31c2d4e97fd09db8ba1a05c5f63803b4c77
Execute tx f39d14a462f6b2eaa2b586d49dc7fc4e974f68f8eecbaf1a5e55ffe7918259b1

Where this interval sits

Longer than 43% of the 5,967 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 2025-10-08 19:41 UTC · block 76,430,661
  2. freeze 2025-10-08 20:04 UTC · block 76,431,117
  3. executed 2025-10-08 20:04 UTC · block 76,431,117

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.