Proposal #6344

freeze · executed

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

Target TXM8gCaGGRJ7zv2v6t1kZ6CFug8BzZfVjJ
Submitted2025-11-10 16:27 UTC
Executed2025-11-10 17:25 UTC
Interval57.7 min
Submit tx b074acfe2f594b073dd51c9ac3c46232e21c5e0fa505f4f2b8b861e6880d2d00
Execute tx 1918c885245583c2e0cb82a122e6b5c378fdf5546030d40ef360eb3bb5758634

Where this interval sits

Longer than 58% 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-11-10 16:27 UTC · block 77,376,925
  2. freeze 2025-11-10 17:25 UTC · block 77,378,079
  3. executed 2025-11-10 17:25 UTC · block 77,378,079

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.