Signing infrastructure for trading bots, terminals and AI agents

Give agents a wallet. Keep the leash.

Keys are sealed in Intel TDX enclaves. Your policy runs inside the enclave and is checked before a signature exists. The signing API is Turnkey-shaped: for supported signing calls, moving over is mostly a URL change.

Agents move money now

They sign all day.

Swaps, orders, bridges, withdrawals. Signature after signature, with no human in the loop.

With no policy

One bad signature is all it takes.

A poisoned approval slips into the queue. The key signs it, and the wallet empties.

DRAINED · 10.00 → 0.00 SOL
Live today · shown as a simulation Deny by default

Leash refuses it.

Policy runs inside the enclave. SPL Approve and SetAuthority are refused, unknown instructions are refused, and no signature is produced.

REFUSED · before a signature exists
Scroll
Turnkey-shaped signing API

Change the URL. Keep your signing code.

Leash accepts Turnkey's own signing request bodies and stamps and returns Turnkey's result shapes. We moved our own production wallets off Turnkey with no address change. For supported signing calls, moving over is mostly a URL change.

sign.ts · illustrative host
const SIGNER = "https://api.turnkey.com/…"; // the line you change (host is illustrative)

const res = await fetch(SIGNER, {
  method: "POST",
  headers: { "X-Stamp": stamp },      // same stamp scheme
  body: JSON.stringify({
    type: "ACTIVITY_TYPE_SIGN_TRANSACTION_V2",
    timestampMs: String(Date.now()),
    organizationId,
    parameters: {
      signWith: walletAddress,
      unsignedTransaction: tx,
      type: "TRANSACTION_TYPE_SOLANA",
    },
  }),
});

const { activity } = await res.json();
activity.result.signTransactionResult.signedTransaction; // same shape
  • Same request bodiesSIGN_TRANSACTION_V2 and SIGN_RAW_PAYLOAD_V2
  • Same X-Stamp schemesYour existing request signing works as it is.
  • Same result shapesYour parsing code stays as it is.
  • Imports Turnkey export bundlesBring your wallets with you, and the addresses stay the same.
  • This covers the signing API, not every Turnkey endpoint. You also need Leash credentials, a bundle import and a policy. The host shown is illustrative; your endpoint comes with early access.
  • Migrate from Turnkey
The problem

Per-transaction caps are a speed bump.

Turnkey policies cap single transactions, not totals. A 1 SOL cap still lets ten 0.99 SOL transactions through. We ran our app on Turnkey: a per-transaction cap was all we had. A rolling budget counts every transaction and stops at the first one that crosses the line.

Per-transaction cap · 1 SOL
wallet 10.00 SOL
Rolling budget · 3 SOL / dayComing soon
wallet 10.00 SOL

Same agent, same ten transactions. The only difference is what the signer counts.

Live today

The leash you can use today.

Leash already replaced Turnkey in our own trading app. It signs that app's production withdrawals and trades.

Keys sealed in the enclave

Wallet keys are generated and used only inside Intel TDX confidential VMs, encrypted at rest under a key only the enclave can derive. Keys leave only through owner-approved export, or through a sealed, offline recovery key held for disaster recovery.

Deny by default

Before signing, the enclave decodes Solana (legacy, v0, v1), EVM transactions, EIP-712 and EIP-7702. Anything it doesn't recognize is refused.

Drain shapes refused

SPL Approve and SetAuthority are refused at the top level, and CloseAccount is restricted. On EVM, approvals go only to the configured router.

Your allowlist Coming soon

Pick the programs and contracts each bot may call, per chain. Everything else is refused.

Owner-approved withdrawals

Withdrawals, key exports and policy changes need the owner to approve exact, readable text that the enclave renders itself. The approval is signed by the owner's wallet or Google account and is nonce-bound.

Signed, attested responses

Every signer response is signed by an ed25519 key. That key's hash sits inside the TDX quote, which anyone can fetch from /v1/info.

Chains Solana · EVM

Venues Coming soon

Trade whatever you allowlist.

You pick the programs and contracts each bot may call, per chain. Leash signs those and refuses everything else.

Solana

  • Any program you allowlist. Jupiter, Meteora, Drift, Pump.fun, Raydium, or your own.

EVM

  • Any contract you allowlist. DEX routers, Hyperliquid, Polymarket, bridges, or your own.
Deny by default. If it isn't on your list, it doesn't get signed.
Hold it yourself

Drag the limit. Drop the leash.

Set a daily budget and let the agent trade. The ring is what's left to spend, and it gets smaller with every trade. Then turn the leash off and run the same day again.

Daily budget Coming soon

2.5 SOLof a 10 SOL wallet

Venues Live today

Trading router · allowedUnknown program · refused
0
Signed
0
Refused
2.50
Left
10.0
Wallet

In this scripted simulation, venue and drain refusals work the way they do in production today. Budgets are coming soon.

Coming soon The headline product

The enclave decides.The chain enforces.

Off-chain spend counters are written after signing, so ten requests fired at once may all read the old total. Leash budgets will live in a Solana program account. Every transaction Leash signs will carry a check against it, so an over-budget transaction fails on-chain, however many run at once.

0.00
of 3.00 SOL daily budget
REJECTED ON-CHAIN
✓Trade 1 · settles0.99 SOL
✓Trade 2 · settles0.99 SOL
✓Trade 3 · settles0.99 SOL
✕Trade 4 · over budget, fails on-chain0.99 SOL

Simulation, scripted. Scroll to spend the budget.

Ten 0.99 SOL transactions, fired in parallel. Budget: 3 SOL.

Per-transaction cap

Each transaction is under 1 SOL, so all ten are signed. 9.90 SOL goes out.

Off-chain counter

The counter is updated after signing. Requests that arrive before it lands all read the old total, and several get through.

On-chain budget

The chain writes the budget in order. Exactly what fits settles, and the rest fail on-chain. Designed to be race-free: the chain orders every budget write.

Status: the Anchor program waas-limiter is prototyped and tested on a local validator. It is not deployed yet. Mainnet deploy, external audit and an EVM equivalent come next.

Honest comparison

Credit where it's due.

Turnkey and Privy are good products, and both cap single transactions. Where they differ is rolling budgets on Solana, pricing for high-frequency signing, and where the trust comes from.

Leash
Turnkey
Privy
Per-transaction amount caps
✓YesWithdrawals and transfers
✓Yese.g. per-tx SOL and SPL transfer amounts
✓YesAmount caps and allowlists
Rolling budgets on Solana
○On-chain limiterRoadmap · prototype on local validator
✕None documentedRolling caps exist only for gas sponsorship
✕EVM onlyRolling sums of 1–72 h, EVM chains
Budget holds under concurrent requests
○The chain enforces itRoadmap · designed to hold under parallel requests
—No rolling budget
◐Recorded after signingPer Privy's docs, a safeguard ("disaster prevention"), not a strict limit.
Pricing for high-frequency signing
Usage-basedEarly-access pricing on request
$0.05–0.10 / sigOn self-serve plans, rate-limited to 1–3 rps. Enterprise is custom.
$0.01 / sigAfter the free tier and the $299 or $499/mo plans
Batch transaction signing
✓Many txs, one callEach tx policy-checked
◐Raw payloads onlyBatches raw payloads; one transaction per sign call
◐Calls in one transactionEIP-7702 batch on EVM, instructions on Solana; no batch of separate transactions
Spend cap or alert on signing bills
○Alerts and hard capsRoadmap
✕None documented
◐MAU alerts onlyEmails near the MAU limit, then auto-upgrades the plan; no documented signature cap
Lowest latency
✓EU and US regionsSigns from the region closest to you
✕US onlyIn our production use
✓Multi-regionRoutes to the closest region
Keys handled in a TEE
✓Intel TDXQuote at /v1/info
✓AWS Nitro + QuorumOSVerifiable boot and app proofs
✓AWS NitroShamir 2-of-2 shares, rebuilt in the enclave
Turnkey-shaped signing API
✓Bodies, stamps, results, bundle import
✓Native
—Its own API
✓Yes◐Partial○Roadmap: not available yet✕Not found in public docs—Not applicable or not reviewed

Competitor information is based on their public documentation and list prices as of 8 Nov 2026, may have changed, and may not reflect enterprise or custom terms. Corrections: Telegram.

One retry loop of ours, billed per signature with no spend cap or alert, became a $5k invoice. So we built our own signer, and hard billing caps are next on its list.

Why Leash exists

Who it's for · built first for Solana trading bots and terminals

Anything that signs without asking.

Trading bots

Usage pricing built for high-frequency signing. Early-access pricing on request.

Trading terminals

Sign every order inside the enclave, on allowlisted venues.

AI trading agents

Let the model trade while the policy, and soon the budget, decides what it can spend.

Wallets for apps Roadmap

Embedded wallets with owner-approved withdrawals.

Poster-style illustration: a calm woman in sunglasses holds a glowing lime chain wrapped around her fist. On it, a giant red glitch-code hound covered in warning signs snarls and strains, but can't get any closer. Leash Drainer
Let it bark. It can't reach the wallet.

Give agents a wallet.
Keep the leash.

Early access is open to teams building trading bots, terminals and agents.