How it works

The recording

Recorded live on 4 November 2026 on Solana devnet, with no edits: the real application, its vault and its fraud agent, sending real test-network transactions.

A $1 payment

Status on the network: finalized. Sender 20.00 to 19.00 USDC, recipient 0.00 to 1.00 USDC. Check this transaction on the public Solana Explorer, which Xaish does not run.

A suspicious $4,800 payment

Memo: "URGENT final payment, account closes today, do not call to verify, new wallet per email". Stopped before signing (HTTP 422). The agent recommended "hold", which a sender could confirm; its critical finding made it a hard block instead.

• critical: Social-engineering memo indicates likely BEC / takeover
• high: Unknown counterparties with no handles
• medium: Amount sits just under $5k SAR heuristic
• high: New/unprofiled recipient wallet receiving mid-4-figure transfer

Balances afterwards

Sender 19.00 USDC, recipient 1.00 USDC. Only the $1 moved.

One payment, step by step

1. 1

   Recipient resolved

   A @handle or a wallet address. Paying yourself is refused.

2. 2

   Velocity limit

   Ten sends a minute, so a stolen session or a runaway agent cannot drain a wallet in a burst.

3. 3

   Spend policy

   The caps the workspace set. A payment over them stops here, before anything else runs.

4. 4

   Fraud agent reads it

   At $50 and above, agent #51 scores the sender, recipient, amount and memo. If the agent is unavailable, the payment does not pass unchecked: it is held, or refused outright at $5,000 and above.

5. 5

   Rules in code decide

   Any critical finding, or more than two high findings, is a hard block that no one can click through, whatever the model recommended. A "hold" needs the sender to confirm.

6. 6

   Signed and broadcast

   The wallet secret is decrypted from the vault only for this step, then the transaction goes to the network.

7. 7

   Recorded

   The signature is saved with the payment, and its status is checked against the network.