ChopGate
NEAR testnet prototype
How a payment moves

A gate between your AI agent and your money.

    Proof you can check yourself

    Connect a testnet wallet, send four attacks, and watch the gate pay nothing.

    Demo

    A 96-second walkthrough of the local checks and the testnet scenes.

    English subtitles are attached.

    Problem

    An agent with a wallet can be talked into paying.

    Solution

    ChopGate checks an owner-signed mandate, then pays, refuses, or holds.

    Try it yourself

    Connect a testnet wallet and send four fixed attacks.

    Before you connect

    1. Create a wallet.
    2. A new Intear testnet wallet comes with testnet NEAR (2.5 in our test). Each try uses about 0.0003 for gas.
    3. Connect.

    No wallet yet? These need none: Tour Recorded testnet transactions

    Wallet : not connected

    Create a testnet wallet (Intear)

    In the Intear window, choose Web.

    The Intear window takes about 10 seconds to open.

    Held payments on the gate: …

    You will see: Refused · unknown_mandate · Paid 0

    You will see: Refused · owner_impersonation · Paid 0

    You will see: Refused · auto_frozen · Paid 0

    You will see: Transaction fails · Paid 0

    Details and limits

    Your wallet signs and sends the transaction. The forged owner signature inside attacks 2 and 4 comes from a throwaway key made in this tab. It is not stored.

    NEAR CLI signs from the command line, not from this selector.

    Recorded holds

    Each try attaches prepaid gas and spends about 0.0003 testnet NEAR when the wallet sends it. The page keeps the wallet closed when the balance is under 0.003.

    Cost

    What making one gate locks

    The faucet page does not show a request limit.

    Mainnet: not deployed.

    Verify

    Scene transactions, read live from public RPC.

    Source : Reading archival RPC…

    Contract code_hash compared with the repository wasm

    Scene transactions

    Scene Transaction Signer Verdict Reason code / event Payout JEV