A private queue
Proposals and signatures stay inside your network. Your team sees the queue; the public doesn't. Publishing to Safe's service is always a deliberate step.
Kagi is the control plane for your Safes, on your own infrastructure. Pending transactions stay private until you choose to publish them, and each one is re-checked against the chain before anyone signs.
Queue
Private to your network·not published
Needs your signature 1
Waiting on others 3
Pause Lending Pool
Ethereum · 1·Nonce 419, next·Call setPaused(true)
Check on your device
Your wallet shows the same values.
Signatures
3 of 5 owners sign on Ethereum.
Signing doesn't execute. Once 3 owners sign, anyone on the team can execute.
Works with the Safes you already have. No migration, no new contracts.
Features
Funds stay in the Safes you already hold, under the same custody. Kagi gives your team a private, verified way to operate them.
Proposals and signatures stay inside your network. Your team sees the queue; the public doesn't. Publishing to Safe's service is always a deliberate step.
Kagi re-reads the Safe at a pinned block, recomputes the hash and refuses known attack patterns. Then owners compare the full hash on their devices.
Owners sign full typed data in the browser, with their usual browser or hardware wallet. No files to pass around. Contract owners sign on-chain.
See balance changes, events and any change to owners or modules before anyone signs. No third-party simulator. If a simulation can't run, Kagi says so. It never shows a pass.
No vendor account and no hosted backend. Kagi keeps working as long as your infrastructure does, whatever happens to anyone else's interface.
Safe's Roles, Delay and guards can already express freezers and risk stewards. Kagi will help you set them up, read them in plain language and test them before they go live.
How it works
Kagi sits between your team and the chain, and trusts neither itself nor any RPC for integrity. Every value is checked where it matters: against the chain, and on the signer's device.
One binary in an environment you control, inside your private network or behind HTTPS with passkey sign-in. It holds pending transactions and signatures, never owner keys.
Owners, balances, nonces and history are read from your own RPC at a pinned block, and simulations run there too. A chain without a node shows as unread, never as empty.
Owners sign with the wallet they already use, on their own device. The hash it shows is the hash Kagi computed from the chain.
OptionalSafe's Transaction Service. Import your pending transactions when you switch over. Publish to it only when you choose.
Security
The largest multisig losses began with a compromised interface and a hash nobody could check. Kagi assumes every layer in between can be wrong, itself included, and checks each value against the chain and the signer's device.
Before any signature, Kagi re-reads the Safe and recomputes the hash from the decoded call. Status is derived from the chain, never stored.
Addresses, hashes and calldata appear in full on every review and signing screen, grouped the way your device shows them.
Delegatecall to unknown code, gas-refund tricks and a second transaction at an already-signed nonce are refused outright.
No telemetry and no third-party requests at runtime. Kagi talks only to the nodes and services you configure. When a check can't run, it stops and says why.
Automations and agent keys can draft and review transactions. Only owners sign.
The Kagi CLI re-checks the same values on a separate machine, with a hardware wallet, for Safes that need it.
Who it's for
Built for the moments when a pending transaction is sensitive in itself: an emergency pause, a treasury move, a change of owners.
Pause a pool, rotate a key or ship an upgrade without announcing it in a public queue first.
Payments, rebalancing and grants in plain language, with exact amounts, a shared address book and one view across chains.
Runs inside your perimeter, keeps an append-only record of every proposal and signature, and alerts you when a guard or module changes.
Tell us how your team runs its Safes. We'll help you set Kagi up on your own infrastructure.