Proposal #6567

freeze · executed

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

Target TKf5o9tyb7G2PZVjp6JujB4gwz2nGY7SPL
Submitted2025-12-03 17:07 UTC
Executed2025-12-03 17:48 UTC
Interval40.6 min
Submit tx 4b7540ebe3cbe22ed926da1ceb2c261f41e902f77b0c71b62e2f2bfcf3acd4a1
Execute tx 6b65aca287a6609cf270aeadc653c68c907a8b6fc8ada6f63ccd03927bc9cd38

Where this interval sits

Longer than 51% 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-12-03 17:07 UTC · block 78,039,919
  2. freeze 2025-12-03 17:48 UTC · block 78,040,732
  3. executed 2025-12-03 17:48 UTC · block 78,040,732

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.