How an over-limit payment gets refused
We gave a spending program a cap: at most 0.01 USDC per payment, to one approved address only. Those rules live in a contract on-chain. Now try it: ask it to pay more than the rules allow, and see what happens.
The rules currently live on-chain
Try making it pay
How is this different from a website blocking you?
- There's no server to bypass. A website can only block what goes through it. Here the rules live on the chain: once the transaction is broadcast, the chain itself makes it fail — even if every server of ours were switched off.
- The money never leaves its owner's wallet. The contract holds no balance; funds move straight from owner to payee. All the contract does is say yes or no.
- We hold no privileges in this contract. No admin, no upgrade switch, no pause button, no withdraw function — the whole contract has just four writable functions, each callable only by the key's own owner. You don't have to take our word for it: the source is publicly verified — check it yourself →
- · Testnet only for now. A third-party security audit comes before mainnet — until then, don't put real money behind it.
- · It governs payments made with this key. A program that holds your wallet's private key can do anything — no contract can stop that. So never hand it your private key.
- · The contract only knows caps, payees and expiry. It doesn't judge whether a payee is dangerous — that's what screening a payee is for.