Proposal #8660
destroy · executed
The multisig announced this 14.7 min before it took effect. That interval is the only warning anyone got.
| Target | TQ2WqdZerVzGKDrRRFNAKqDdu2XmtEkC4B |
|---|---|
| Submitted | 2026-05-01 17:01 UTC |
| Executed | 2026-05-01 17:16 UTC |
| Interval | 14.7 min |
| Submit tx | 516be415181d27d09bc84b0940f50919ca2598e4e43e46498c814413f5f59614 |
| Execute tx | b0eacc7f5426259b75cb4a9ec7b55684701c421c529dc755afb099684f4e97d2 |
Where this interval sits
Longer than 39% of the 5,922 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
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