trustset

The trust stack
for AI agents.

Like the controls on your bank card, for an AI agent. Freeze it, give it an end date, choose who else can freeze it, and see every move it made. Apps on Monad that check follow your settings from the next block.

Try it on testnetSee your agents

Eight layersImmutable, no admin128,000 fuzzed callsMonad testnet

Market maker #7
0x90f7…b906
Treasury sweeper #3
0x15d3…6a65
Research bot #12
0x9965…a4dc
An agent trading on its own

An agent with a key can trade, pay and sign for as long as it runs.

  1. Nothing could stop it.
  2. Nothing could stop it while you slept.
  3. Nothing could stop it without a signature.

Three steps. Then it is done.

Your wallet
Your agent0x90f7…b906 signing
The switch
unset
Every app
Kuru · swap
Perpl · open
Aave · borrow
the key signs on its own. nothing can stop it.
  1. 1

    Your agent already has a wallet.

    It signs with a key. That key is the agent, as far as the chain is concerned.

  • Never runs your agent.
  • Never holds your money.
  • Never sees a private key.

You built the agent. Here is everything around it.

The trust stack: eight things it should have had from day one, each at the hour you would need it. One day, in clock order. None of them need you to change a line of the agent.

trustset.silknodes.io03:00 · The switch
block 275Agent 14 · activeTrading
Kuru · swapAllowed
Perpl · open positionAllowed
Aave · borrowAllowed
nad.fun · buyAllowed
Governance · voteAllowed

03:00 · The switch

It is 3am and the key has leaked.
One transaction. Off from the next block.

Your wallet pauses or stops it, and every app that checks refuses that key.

03:40 · Human proof

A transfer just went out.
Was it you, or the agent?

A passkey signs that exact action, so anyone can later ask whether a person was there.

07:00 · Limits

You forgot the agent was still running.
Trust that ends by itself.

An end date, or a heartbeat it has to keep. Miss either and trust lapses on its own.

08:10 · Identity

A venue meets a key it has never seen.
It can still ask whose agent that is.

Its ERC-8004 identity points back at the switch, so any app can ask whether it was stopped.

14:35 · Past signatures

An order arrives, signed before the stop.
Judged by when it was signed.

A stop at 14:32 voids the 14:35 order and honours the 14:30 one.

19:40 · Panic button

You need it stopped, not signed.
A fingerprint is enough.

A passkey on your phone pauses it, and can do nothing else.

21:15 · Refunds

It was mid-payment when you stopped it.
The money comes back.

A payment still unsettled when its window closes goes back to the payer, and anyone may send it.

23:50 · Guardians

You are asleep and something is going wrong.
The people you chose can stop it.

Guardians pause it by vote. They can never spend from it, and your wallet overrules them.

Do not take our word for it.

Six claims, and where to check each one.

trustset · what you can check
reading the chain…
  1. 01

    We never hold a key that can spend

    Your agent's private key and your wallet's never leave you.

  2. 02

    A contract, not our server

    One view call against Monad, with nothing of ours in the path.

  3. 03

    Refused inside the venue's own call

    The check and the action are the same transaction.

  4. 04

    The passkey never leaves your phone

    Only the public half goes on chain, bound to this site.

  5. 05

    Guardians pause. They cannot take it

    A handover takes a threshold plus a delay you can refuse.

  6. 06

    Stopped for good stays stopped

    128,000 fuzzed calls a run try to undo it and cannot.

The whole integration. One line, inside your own call.

Solidity
// inside your own function, before you act for an agent
if (!killSwitch.isTrusted(agentId)) revert AgentNotTrusted(agentId);

A stopped agent is refused inside your transaction, so nothing upstream can skip it. Addresses and the rest in the docs.

An agent with an ERC-8004 identity can point at its switch under one metadata key, and the explorer links them automatically.