Proposal #6901

freeze · executed

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

Target TSEgF86ogBWtfRJXFYMq1hrCpU4Px1fT5u
Submitted2026-01-22 21:11 UTC
Executed2026-01-22 22:11 UTC
Interval59.6 min
Submit tx 6c2ded076ccfcc0ad25d16785130862d25c1165cc8317a2015014360ebf06ba9
Execute tx 70be0d41e6acdd539a46f7291e28228a59f8ee4c0cb1a6545cb528963c544db8

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 2026-01-22 21:11 UTC · block 79,484,132
  2. freeze 2026-01-22 22:11 UTC · block 79,485,325
  3. executed 2026-01-22 22:11 UTC · block 79,485,325

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.