Proposal #6671

freeze · executed

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

Target TAySoap43zAWFj8CDi7UaWAG6UVEzGDvRz
Submitted2025-12-17 19:33 UTC
Executed2025-12-17 20:26 UTC
Interval53.8 min
Submit tx ab72e76649eb48a4edda3e0ca5644be2b0d910d11c1fa0e1eead67aadce57948
Execute tx a8a7e465c4bb5b08bae7aba184f93a2c83309acf2cb71e3109bfba8f76de2857

Where this interval sits

Longer than 56% 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.

Part of a batch. 1 other proposal went out within ten minutes either side of this one. Freezes are issued in sweeps, not one at a time — so this address was probably not singled out. See the whole sweep.

What happened on chain

  1. proposal 2025-12-17 19:33 UTC · block 78,445,920
  2. freeze 2025-12-17 20:26 UTC · block 78,446,996
  3. executed 2025-12-17 20:26 UTC · block 78,446,996

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.