Steve Docs

Wallets and Signing

The non-custodial wallet model, transaction previews and approval thresholds.

Steve is non-custodial by design. Your keys stay in your browser wallet, and the agent only ever prepares transactions for you to sign.

How a transaction flows

The agent decides an action is needed (for example a swap or a launch).
The tool call returns an unsigned transaction built by the gateway.
Steve decodes it and shows you a Transaction Preview: every instruction, every amount, the fee payer and the risk class.
You sign in your browser wallet, or you reject. There is no third path.

Approval thresholds

Actions below a configurable threshold can be prepared and executed with minimal friction because they are simulated and policy checked first. Actions above the threshold always require an explicit signature. The threshold is part of your mandate, not a global constant.

The simulation gate runs before approval: the transaction is constructed and simulated without signing and without broadcasting. If the simulation fails, the action is blocked and the blocked decision is recorded.

If a preview does not match what you asked for, reject it and ask the agent to explain. Every tool call in the conversation history shows exactly which tool produced the transaction.

SIWS sessions

Sign In With Solana proves wallet ownership and creates your agent session. The signature grants no spending rights. Sessions expire, and financial actions always re-verify against the live wallet state before building a transaction.

What the agent can never do

  • Sign transactions. There is no agent side key.
  • Move funds without your signature above your configured threshold.
  • Touch other wallets. Sessions are isolated per wallet.