Chatito
← Blog

· 6 min · Chatito

Self-Custody on Chatito

Self-custody on Chatito means you hold the funds. Automation software, not a bank. Keys, Propose and Sign, and Smart Policy explained clearly.

self-custodyproductsmart-policysecuritychatito
Self-Custody on Chatito

Who Holds The Money

Self-custody on Chatito is simple on purpose: you hold the money. Chatito is automation software for rules, sampling, and execution limits. It is not a bank, not a broker that takes deposits, and not a vault. If someone tells you to send tokens to Chatito so the product can trade for you, that is not this model.

This post is a trust map. It walks the three different kinds of credentials the product talks about, what each one can and cannot do, and why seed phrases never belong in the UI. It is educational, not an invite to Sign a grant or arm Live today. For the canonical detail, read Custody and Keys.

The Spine: Control Stays With You

Manual trading turns every candle into a negotiation with yourself. Strategy-first tools try to fix the process, not replace your wallet. The same doctrine applies to custody: invent and prove rules, keep capital under your control, automate only inside limits you set.

Self-custody crypto trading, in the Chatito sense, is not a slogan on a landing page. It is a set of hard separations:

Separation Meaning
Software vs funds Chatito runs logic. You keep balances.
Credentials vs seeds Trade keys or policies are limited. Recovery phrases are never requested.
Saving vs Live Storing a setting is not arming size. Live is a separate switch.
Rules vs blank check Caps, expiry, and recipient locks bound remote action.

Run the system, not the dopamine. That only works if the system cannot quietly become the custodian.

Three Different Keys (Do Not Mix Them Up)

People say keys and mean one blob of risk. Chatito splits the world into three lanes. Confusing them is how bad mental models (and bad products) get built.

1. Exchange API Keys (CEX)

On centralized venues, balances stay on the exchange under your account. Chatito may store encrypted trade credentials so a strategy can place and manage orders inside whatever permissions you issued on the exchange side.

Important honesty checks:

  • Saving a key is configuration. It is not Live.
  • Scope keys the way a careful operator would: trade permission where needed, withdraw permission only if you truly intend it (most operators never do for bots).
  • Revocation lives on the exchange. If you kill the key there, remote trade access dies with it.

Chatito is still not holding your CEX balance. The exchange is. The product is talking to the exchange with credentials you chose to attach.

2. Propose And Sign (LP Default)

For LP-style flows, the default posture is you sign every action. Mint, collect, rebalance, close: each step is a proposal you approve in your own wallet.

No open-ended grant is required for that path. You remain the signer. The software prepares the work. You decide whether the transaction leaves your wallet.

That is slower than a blank-check bot. It is also honest. Speed is not a reason to collapse custody into convenience theater.

3. Smart Policy

Smart Policy is the limited remote-control lane. You define the rule set. In the product model, you sign that rule once. A keeper may act only inside what you allowed: cap, expiry, recipient lock, and the rest of the policy surface documented there.

Tokens and NFTs stay in your wallet. The policy is not a deposit box. Chatito is not a vault. You should never deposit into Chatito as if it were an account balance the company holds for you.

Public Smart Policy Sign is audit-locked. This article explains the model so you can evaluate it. It is not a call to Sign a grant in production today.

Cousins, Not The Vault Door

CEX API keys and Smart Policies are cousins in one narrow sense: both are limited remote control, not the master key to your life savings.

Control type Where funds live What remote side can do
CEX API key Your exchange account Whatever the key permissions allow
Smart Policy Your wallet Only inside policy caps and locks
Seed phrase Entire wallet tree Everything. Never share it.

The vault door is your seed phrase and your exchange master login. Chatito does not ask for seed phrases. Never paste a recovery phrase into Chatito, into a support chat, or into a look-alike site. Support will never need it. Anyone who asks is running a theft script, not onboarding.

What Chatito Is Not

Clarity beats marketing fog:

  • Not a bank. No customer deposits as a product feature.
  • Not a vault. Do not treat a policy or an API field as a place you send funds for safekeeping.
  • Not custodial yield. If a flow needs capital, it is your exchange balance or your wallet under your signatures and policies, not a Chatito-held pool.
  • Not Sign-today theater. Audit lock means we teach the design without pretending the public Sign button is the homework for this week.

Live remains a separate switch from saving credentials or drafting rules. Configuration is not permission to size up. Invent and prove process before you scale live size. That sentence is about risk psychology and about custody: do not blur them.

Practical Habits That Match The Model

Education only sticks when it becomes checklist behavior.

  1. Separate mental buckets. Exchange account risk, wallet risk, and automation risk are different. Label them in your own notes.
  2. Least privilege. On CEX keys, strip withdraw if you only need trade. On policies, tight caps and short expiry beat infinite convenience.
  3. Never seed in browser forms. Hardware wallet or clean recovery storage only. Chatito UI is not a seed manager.
  4. Revocation plan. Know how to delete an API key on the exchange and how a policy ends (expiry, revoke paths as docs describe).
  5. Paper and sample before size. Custody design does not save a broken strategy. It only keeps a bad day from becoming a wrong-custodian day.

Strategies over emotions includes the emotion of impatience. Rushing to grant wide control so the bot feels alive is still dopamine, just wearing an ops badge.

How This Fits The Product Story

Chatito's loop is build, sample, kill or promote, then automate once rules are stable so you stop negotiating with yourself on every candle. Automation that requires you to hand over custody would invert the story: the system would own the dopamine and the funds.

So the custody model is not a side FAQ. It is load-bearing infrastructure for the doctrine. Human keeps capital control. Software enforces the plan inside limits. Lab and policy tooling improve the book. They do not become the bank.

When you read feature pages later, keep asking one question: where do tokens sit when nothing is happening? If the answer is still your exchange account or your wallet, you are in the self-custody frame. If a product needs you to send funds into its contract as a balance it holds for trading, that is a different product class. Do not map that class onto Chatito.

Read The Docs, Then The Waitlist

For the full custody surface, start here: Custody and Keys. For the rule-bounded keeper model, read Smart Policy.

When you need to stop negotiating with yourself on every candle, Chatito is the system. Paper first. You arm live. Keys stay yours.

Join the waitlist if you want the system, not another feed. Learn the model first. Do not treat a blog post as a signing checklist.

Not financial advice. Trading, automation, and prediction markets involve risk of loss. Past or paper results do not guarantee future performance. You are responsible for how you store seeds, issue exchange keys, and evaluate any policy design before you use it.


Not financial advice. Trading and prediction markets involve risk of loss. Past or paper results do not guarantee future performance.

FAQ

Does Chatito hold my funds?
No. Chatito is automation software, not a bank or deposit taker. Balances stay in your exchange account or your wallet depending on the venue. It is not a vault, and you should never deposit into Chatito as if it were a custodial balance.
What is the difference between an exchange API key and a Smart Policy?
An exchange API key lets software talk to your CEX account under the permissions you set; funds stay on the exchange. A Smart Policy is a rule-bounded wallet-side control: tokens stay in your wallet and a keeper may act only inside caps, expiry, and locks you defined. Both are limited remote control, not your seed phrase.
Will Chatito ever ask for my seed phrase?
No. Never paste a recovery phrase into Chatito or into anyone claiming to be support. Seed phrases open the whole wallet tree. The product model uses exchange credentials or explicit wallet signatures and policies, not seed custody.
Is saving API keys the same as going Live?
No. Saving encrypted trade credentials is configuration. Live is a separate switch. Do not treat stored keys as permission to scale size. Prove process before you scale live size.
Can I Sign a Smart Policy on the public product today?
Public Smart Policy Sign is audit-locked. Read the Smart Policy and Custody docs to understand the model. This showcase does not invite you to Sign a grant or arm Live from the blog.
Where should I go next if I care about self-custody on Chatito?
Read https://chatito.com/docs/custody-and-keys and https://chatito.com/docs/smart-policy, then join the waitlist on https://chatito.com for product updates. Prioritize understanding over rushing credentials.

Not financial advice. Trading involves risk of loss. Paper ≠ live.