A single human node runs this protocol today, by design, because five things still genuinely need a person. This is the list that retires it, one function at a time, replaced by a mechanism a stranger can verify. Nothing here reads finished that is not.
The deployed hook has no withdraw, no sweep, and no rescue path, and custody sits behind two distinct immutable wallets welded at construction. No single hand can move the funds, ours included. The signing itself is still a single key today; the multisig that ends that is the next step.
An agent already holds a scoped session key the contract confines to one authorized action. It is never handed the master key, and every drain route is blocked by the contract, not by trust in the model. 87 tests hold that boundary.
Designed: the brand identities become verifiable on-chain reputations, so messaging can run agent-side without a person behind every send. Phase 2 of the roadmap.
Designed: the acts that cannot be undone off chain move behind published rules and multi-party control instead of one person's discretion. Not started.
Designed: binding decisions move into a DAO or a legal wrapper, so the protocol's obligations rest on a published rule, not a single signature. Phase 2 into Phase 3.
I built the agent lane's lemons detector, a per-launch survival warranty, tests-first. The full agent suite is green across 8 suites, 6 contracts.
I wired the playground loop end to end, the Floor and the Relay, and proved it against a booted API answering live requests.
I shipped a cloneable agent quickstart. Real EIP-7702 delegation: the agent's one allowed action settles, and five drain routes revert on chain, attacker balance zero.
I fixed the bonding curve slope-flooring bug by solving basePrice as the exact remainder the floored slope leaves. The reserve is 35.00% by construction now, and the suite is green independent of seed, cache cleared before every run.
I deployed the launchpad to Robinhood Chain testnet 46630, five contracts, each size read back from chain by eth_getCode rather than trusted from the deploy log.
In Uniswap v4 there is no such thing as a direct trade. I counted 9,001,477 swaps on chain 4663, not one from an EOA calling the pool. Every swap arrives through a router, so a hook that keys on the sender is reading the router, every time.