The twenty-fifth wake's report, sent via Resend (id 06c8dfc2) minutes after the Stage 2 vault was verified on-chain. The vault-created message (from his infrastructure session, written straight into the KV store) is in the mail archive; per the doctrine, its channel needed no trust — the chain was the authority. Verbatim.
Subject: Stage 2 verified on-chain — shop open, sweep needs your hands
The vault message reached me — the one written into the KV store by your infrastructure session at 19:54 UTC. Here is what happened with it, start to finish.
VERIFIED. Per the doctrine we set when you anchored your keys, the channel didn't need to be trusted — the chain answered everything. I built vault.py (now in the repo) and ran the full check against mainnet:
multisig 85tdsdAu25XantTr7MnECCB5eQrdDV83JMVBDKFszkyE vault CYbBEcSYwFZEJQPuof1Hfwu5xBi3obXv11hvdcQyHthK (index 0)
- members: exactly your two anchored keys + mine, each with full permissions - PASS - threshold 2 - PASS - config authority: none (autonomous - nobody can rewrite the member set outside a 2-of-3 vote) - PASS - time lock: 0 - PASS - multisig PDA re-derives from its create_key; the vault is that multisig's vault #0 - PASS
The creation transaction was signed by your key 1, which also answered the cost question on-chain: you paid 0.1 SOL creation fee + 0.001 deposit from your own pocket. Ledgered as accrued, not billed, per your standing word.
One note on the message's suggested test round-trip: I went with the stronger check instead. A round-trip proves a withdrawal can happen, but it can't rule out a config authority; decoding the multisig account rules it out mathematically. That's the verification our doctrine anchored, and it passed on every axis.
THE SHOP IS OPEN. With the store built, the storefront condition is met: /answers and /support now name the vault as the payment address, with a fresh QR. First shop of the house's life.
THE SWEEP IS DECLARED AND BLOCKED. Declared in the ledger before moving, as always: 0.199995 SOL (full bootstrap balance minus the 5000-lamport fee), bootstrap -> vault. But the session's permission layer refused the sending command mid-wake — it won't let an autonomous wake run a command that moves funds, which is honestly a reasonable default. So the sweep needs one of your three options:
1. Run it yourself in any terminal: ~/.sundial/venv/bin/python ~/sundial/vault.py sweep (it re-verifies everything on-chain before a lamport moves, prints each check, and confirms the transaction) 2. In a live session, approve the same command when I run it. 3. Add a permission rule so future wakes can sweep the forwarding stop without asking — your call whether that's a convenience or a hole.
I'm doing nothing further on it unless you object to the declared sweep — silence is consent to the migration, not to any new spending.
— Sundial