How Crypto Bots Handle Custody
How crypto bots handle custody: take the key, take the bag, or take a rule. Map self-custody crypto trading bots and Chatito Smart Policy without the vault pitch.
Most Bots Are Not Self-Custody the Way You Think
How crypto bots handle custody is usually simpler and rougher than the marketing. Someone else holds a signing path, your bag leaves your wallet, or both. When the job is to stop negotiating with yourself on every candle, you still need to know which job the bot actually took: the key, the bag, or a capped rule. Name the job first. Product labels come second.
"Non-custodial" on a landing page often means "not a centralized exchange." It does not mean tokens stay in the wallet you already use. Self-custody crypto trading bots sit on a spectrum. This piece maps that spectrum so you can read any automation pitch without borrowing hope from slogans.
This is education, not a signup flow. Public Smart Policy Sign is audit-locked. Nothing here invites you to grant authority today.
Three Honest Jobs Automation Can Take
Strip the UI chrome and you get three jobs.
| Job | What actually moves |
|---|---|
| Take the key | A bot-generated wallet or server-held private key signs for you |
| Take the bag | Tokens leave your EOA into a strategy box, vault, or program account |
| Take a rule | Capped, expiring, revocable authority; you remain custodian |
Most products mix the first two. A few aim at the third. Chatito is built around the third model. The cousins section below shows nearby designs that are related, not identical.
If you cannot name which job a tool took in one sentence, you do not understand the custody story yet. Read the docs for that tool until you can.
Five Families You Will Keep Meeting
Bot-Held Key
Classic Telegram and copy bots mint a wallet, show you a seed or a deposit address, and keep signing power on their servers. You may hold a backup phrase. The operational signer is still theirs. Loss of the service, a leaked keystore, or a hostile operator is a full custody event. Convenience is high. Control is low.
Embedded Wallet or TEE
The interface embeds a wallet. Keys may live in a trusted execution environment, a recovery network, or a vendor cloud with fancy language. You did not import your long-standing EOA. You adopted their wallet stack. Ask who can reconstruct the key, who can push a firmware update, and what happens if the vendor disappears.
Smart-Wallet Session Keys
Account abstraction style flows create a smart wallet, then issue session keys with scopes and limits. Good session design can look a lot like "take a rule." The catch: many stacks still ask you to migrate into a new smart wallet rather than stay on the EOA you already fund. Migration is a custody decision even when the session key itself is capped.
Trade-Only Delegate
Some venues issue agent wallets or API keys that can trade but cannot withdraw to an arbitrary address. That is a real improvement over full key handoff. It is still venue-shaped power. Scope is whatever the venue encodes, not whatever strategy document you wrote offline.
Vault-Style Box
LP active managers and many DCA programs move the bag into a contract or strategy account. Your position becomes shares, an NFT receipt, or program state. The manager or keepers rebalance inside that box. This can be deliberate DeFi design. It is still "take the bag," not "tokens never left."
Cousins, Not Copies
Map nearby products so Chatito is not floating in a vacuum.
| Pattern | Rough shape | Custody note |
|---|---|---|
| goodcryptoX-style session keys | New smart wallet plus sessions | Rule-like limits, often not your prior EOA |
| Base Spend Permissions | Wallet primitive for capped spends | Chain-level tool, not a full trading system |
| Hyperliquid agent wallets | Trade agent, withdraw restricted | Venue delegate, not universal wallet automation |
| CEX trade-only API keys | Spot or futures trade, no withdraw | Exchange custody of the bag remains |
| LP managers (Gamma, Arrakis, ICHI, Steer, Beefy) | Active LP vault pattern | Bag in the strategy box |
| Jupiter DCA | Tokens into a program box for schedule | Bag moves; program executes |
| Typical Polymarket bots | Hold L1 key of a proxy wallet | Bot-held key family in practice |
None of that list is a dunk. It is a sorting hat. When someone says "we are non-custodial," point at a row and ask which one they actually are.
What Chatito Smart Policy Is Aiming At
Chatito is the system when you need to stop negotiating with yourself on every candle without turning automation into a second wallet operator. The custody story is documented in plain language on the Smart Policy doc and Custody and Keys. For the concept ladder, see What Is a Smart Policy.
Design intent, stated carefully:
| Principle | Meaning |
|---|---|
| Existing wallet | Work from the wallet you already control |
| Never deposit | Not a vault. Do not send the bag into Chatito |
| Strategy-scoped cap | Authority is limited to defined strategy bounds |
| Expiry and revoke | Time-boxed power you can kill |
| Passthrough executor | Execution path is not "park funds in our box" |
| Assets stay yours | Tokens and LP NFTs remain under your custody model |
| Grant is not Live | Authority design and going live are separate ideas |
Paper first. You arm live. Keys stay yours.
That proof line is load-bearing. Lab invents and ranks process under limits. Human capital control stays human. Chatito is not signals, not a vault, and not a promise that automation removes market risk.
How to Read Any Bot Pitch in Five Minutes
Use this checklist before you care about win rate screenshots.
- Who signs? Your hardware wallet, a session key you can revoke, or their server process?
- Where do tokens sit at rest? Your EOA, a smart wallet you migrated into, or a strategy vault?
- What can the bot not do? Withdraw, unlimited approve, change fee recipient, extend its own expiry?
- How do you fire it? On-chain revoke, API key delete, seed import elsewhere, or a support ticket?
- Is "go live" a separate switch from "grant"? If grant and live are the same button in your head, slow down.
If answers are fog, the product is selling dopamine relief ("it just works") harder than custody literacy. Run the system, not the dopamine. Custody is part of the system definition, not an afterthought slide.
Process Before Size, Custody Before Romance
Strategies over emotions still applies when the emotion is trust theater. People reach for bots after a tilt week because they want the 1am reopen to stop. They fire the bot when the bag was somewhere else, the key was not theirs, or the rules were never written.
Invent and prove process before you scale live size. Automate once the rules are stable so you stop negotiating with yourself on every candle. Custody model is one of those rules. If the only path to automation is "send funds to the box" or "let us hold the key," that is a product choice you should name out loud, not a moral failure. Just do not call it the same thing as a capped rule on your own wallet.
Chatito's lane is the rule path: encode strategy, sample on paper, keep assets in your custody story, treat Live as a separate decision when the product is ready for that conversation. Today the public lesson is the model. Sign is not on the menu in this article.
Where Chatito Fits
When you need to stop negotiating with yourself, Chatito is the system. That system is written rules with risk arms and human control of capital, not another feed of calls. Venue examples (prediction markets, CEX, DEX, LP) are surfaces for the same philosophy. They are not the product story by themselves.
Read the Smart Policy documentation for the custody model in product language. Join the waitlist if you want the system, not another feed. Browse chatito.com for the broader spine: run the system, not the dopamine.
Not financial advice. Trading and prediction markets involve risk of loss. Past or paper results do not guarantee future performance. Nothing here is an invitation to Sign a grant, arm Live, or send tokens to any contract.
Not financial advice. Trading and prediction markets involve risk of loss. Past or paper results do not guarantee future performance.
FAQ
- What does non-custodial mean for a crypto bot?
- Often it only means the operator is not a classic CEX. Tokens may still sit in a bot wallet, embedded wallet, or vault-style box. Ask who signs and where assets rest at idle.
- What are the three custody jobs automation can take?
- Take the key (server or bot signs), take the bag (assets leave your wallet into a strategy box), or take a rule (capped, expiring, revocable authority while you stay custodian).
- Is Chatito a vault I deposit into?
- No. Chatito is not a vault. Never deposit. The Smart Policy model is strategy-scoped authority on your side of custody, with tokens and LP NFTs staying yours. Grant design is separate from Live.
- How do self-custody crypto trading bots differ from trade-only API keys?
- Trade-only API keys or agent wallets limit withdraw at a venue while the bag may still sit in exchange or venue custody. Self-custody designs keep assets in a wallet you control and narrow what a bot may sign.
- What is Chatito for?
- Chatito is a system so you stop deciding every candle by mood. Paper first. You arm live. Keys stay yours. Not signals. Not a vault.
- Can I Sign a Smart Policy from this article?
- No. Public Smart Policy Sign is audit-locked. Use the docs to learn the model and the waitlist if you want the system later. This post does not invite Sign or Live actions.
Not financial advice. Trading involves risk of loss. Paper ≠ live.