Wallets & security
How your Torch wallets are held, what signs automatically, multi-wallet, export, and what Torch can never do.
Custody model in one paragraph
Each Torch account gets its own isolated organisation inside Turnkey, a key-management service that runs signing inside hardware secure enclaves. Your keys are generated there and never leave. Your password unlocks a root credential on your own device; that credential is what approves sensitive actions. Torch's servers hold a limited, policy-bound permission that lets them sign routine trades under your threshold and nothing else.
Two authority levels
| Action | Who signs | What you see |
|---|---|---|
| Buy / sell / swap under your auto-approve threshold, to an approved trading router, to your own wallet | Torch, automatically | Trade just happens |
| Automated orders (TP / SL / limit / DCA) when they trigger | Torch, automatically | Notification on fill |
| Trades above the threshold, or when the hourly auto-sign budget is used up | You, with your password | "Confirmation required" and a button that opens the Torch app |
| Withdrawals, bridges above limits, token launches, threshold changes, policy updates, key export | You, with your password | Always asks |
The threshold is yours to set in Settings. There is also a rolling hourly budget for automatic signing; once it is spent, the bot simply asks for your password until it resets. That is a safety rail, not a lockout.
What Torch cannot do
- Read or reset your password.
- Export your private key.
- Change its own permissions on your wallet. Policy updates need your password.
- Send funds to an address other than your own wallet or an approved trading router without your confirmation.
- Sign transactions above the per-transaction cap, no matter what.
Addresses
- One EVM address for every EVM chain. Funds on Base and funds on Robinhood Chain sit at the same address but are separate balances.
- One Solana address, from a separate key. It is never derived from the EVM key.
/security in the bot repeats this summary at any time.
Multiple wallets
/wallets lets you keep up to 10 wallets per account.
- Create a new EVM or Solana wallet and give it a label.
- Activate one; the menu header and every trade screen use the active wallet.
- Remove any wallet except the first one. Removal hides the wallet from menus; it does not destroy the key. Export first if it holds anything.
- Token cards show
◀ 👛 Label (n/m) ▶so you can switch wallets without leaving the card.
Export your keys
/exportkey (or /export) opens the in-Telegram app. The key is decrypted on your device; the bot backend never sees it. EVM and Solana keys are exported separately, so do both.
Nobody from Torch will ever ask for your key
Support never needs your private key, seed phrase or password. Anyone asking for them is not Torch.
Importing a wallet
Not supported. Torch wallets are always generated inside the enclave so the guarantees above hold. To trade with existing funds, send them to your Torch address.
Withdraw
/withdraw sends native tokens or ERC-20 / SPL tokens to any address. Address format is validated against the asset's chain (an 0x address will not be accepted for a Solana asset). Withdrawals always ask for your password.
Update wallet policies
When Torch adds a chain or a trading router, the permission set on your wallet needs a one-time refresh. The bot tells you: Wallet security policies out of date. Go to /settings → Update Wallet Policies and confirm with your password. Until then, automatic trades to the new destination are refused by the enclave, while password-confirmed actions still work.