Binonce

With Chainwall

The same stolen-key trick, aimed at money kept in a Chainwall vault instead of a plain wallet. The vault checks who is asking before it moves anything, so when a signer has been taken over, it says no.

Ready · server-signed walkthrough
Step 1 of 5·preview

The money goes into a vault with rules.

Instead of sitting in a wallet that obeys any signature, the funds sit in a Chainwall vault. It only moves money through actions its policy already approves, and it checks who is asking every time.

Vault, registry and engine addresses will appear here.
Live logempty
$ binonce defend --chain 1874
Waiting. Press Run defense to start.

Sign it yourself

Connect your wallet from the top bar

Connect the operator wallet and sign a real payout from the Chainwall vault. Then hijack your own account with EIP-7702 and sign again — your wallet still produces a signature, but Chainwall refuses it.

Connect the operator wallet to sign.

Multisig treasury console

The same vault as a full 2-of-2 treasury: a relayer proposes a transfer, two wallets sign it on-chain, and a 1,000,000 USDC spending-cap policy blocks anything over the limit.

Connect a treasury-owner wallet from the top bar to begin.
1

Propose a treasury transfer

A relayer proposes the transfer. It then needs both treasury signers to approve — a real 2-of-2, enforced on-chain, plus a 1,000,000 USDC spending cap.

2

Two wallets sign

OwnerPending
0x3ae7…5749
Approver 2Pending
0xcBAe…A614
3

Execute