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.
They sign all day.
Swaps, orders, bridges, withdrawals. Signature after signature, with no human in the loop.
One bad signature is all it takes.
A poisoned approval slips into the queue. The key signs it, and the wallet empties.
Leash refuses it.
Policy runs inside the enclave. SPL Approve and SetAuthority are refused, unknown instructions are refused, and no signature is produced.
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.
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 bodies
SIGN_TRANSACTION_V2andSIGN_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
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.
Same agent, same ten transactions. The only difference is what the signer counts.
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
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.
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
Venues Live today
In this scripted simulation, venue and drain refusals work the way they do in production today. Budgets are coming soon.
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.
Simulation, scripted. Scroll to spend the budget.
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.
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.
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
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.
Give agents a wallet.
Keep the leash.
Early access is open to teams building trading bots, terminals and agents.