The mechanism works.
Here’s the proof.
foonBTC’s custody isn’t a promise — it’s a mechanism we ran end-to-end on-chain: 10 real 3-of-5 Gnosis Safes, a full genesis → propagate → wave lifecycle with actual multisig-signed transactions, and a supply invariant that held to the unit. This page publishes that run. Every address below is a throwaway devnet artifact with no live value — a demonstration, deliberately not a live custody map.
Six steps, every one a real on-chain action.
Executed 2026-07-24 on devnet 36927 (local anvil — throwaway). Each propagate and wave move is a genuine Safe.execTransaction signed by that cluster's 3-of-5 — not a simulation.
Ten independent 3-of-5 vaults, hot and cold.
Each cluster is its own Gnosis Safe with 5 owners and a threshold of 3 — no single key moves funds. Hot tier (A–E) serves payouts; reserve tier (F–J) backs them. This is the exact custody shape foonBTC's mainnet reserve will use, born from the council seed rather than these devnet keys.
Deployed contracts (devnet).
The Safe stack and demo token this run deployed. Throwaway addresses on a local devnet — published so the run is fully checkable, not because they hold anything.
What this proves — and what it deliberately isn't.
The custody mechanism runs end-to-end on-chain: real multisig Safes, real threshold signing, a real lifecycle, an invariant that holds. Not slideware — executed.
A live custody map. Every address is a devnet throwaway with no value. Mainnet foonBTC custody uses Safes owned by the council seed, on the real chain, and those addresses are not published here — deliberately.