⏱️ How fast do the five Safes move today?

Safe (alias) Threshold Executed txs Median ⌛ to execution Mean ⌛ St-dev Previous-owner executions
0x9F6e…(Council Safe) 6 / 9 434 10 h 42 m 11 h 37 m 7 h 18 m 86 %
0x71E4… (Treasury Safe) 5 / 9 735 8 h 45 m 9 h 51 m 6 h 46 m 75 %
0x2ff7… (IG Safe) 5 / 9 95 7 h 16 m 8 h 36 m 6 h 35 m 87 %
0xd55c… (MG Safe) 5 / 8 193 2 h 18 m 7 h 08 m 8 h 37 m 43 %
0xf642… (Foundation Safe) 6 / 10 20 15 h 10 m 11 h 41 m 7 h 53 m 85 %

Key patterns

  1. Time-to-execution is dominated by waiting for signatures, not gas-paying. The gap between the last signature and the execTransaction call is ≤ 1 block in almost every tx.
  2. A handful of people create most of the backlog. Every Safe has a “power signer” who initiates 30–60 % of proposals and pays most gas. When that account is awake, things move; when they sleep, the Safe stalls.
  3. Variance is huge. St-devs of 6–8 hours mean some txs clear in minutes while others linger a full day—a red flag for time-critical ops.

⚙️ What to tweak to ship faster —and why it works

Bottleneck Practical fix Why it helps
Sleeping signers in one time zone Rotate at least one signer per major time zone. Keeps a quorum awake 24 × 7 so proposals don’t sit 8 h overnight.
Nobody notices new txs 1️⃣ Enable Safe webhooks / Slack bot for “Tx created” pings. 2️⃣ Auto-DM lagging signers after N minutes via Telegram or PagerDuty. Reduces “human latency”; Delta’s 2-hour median shows what happens when signers react quickly.

🚀 Quick-win action list

  1. Stand-up the Slack / Discord Safe bot and set SLA: “Sign within 60 minutes during office hours”.
  2. Move two current “power signers” into opposite time zones (or notify volunteers) before any next large event that could require speed.

Target - we should push median execution below 2 hours across every Safe—without weakening security where it matters.