Why Custodial Bots Are Dangerous
// Their bot holds your funds. Ours holds nothing. The safest hands for your keys are your own — here's the honest case, including what self-build does NOT fix.
You can't outsource trust. The safest hands for your keys are your own.
A trading bot has to act on an exchange. The question is whose keys it acts with. A custodial bot — one you deposit into, or hand a withdraw-enabled API key — acts with control over your funds. A self-built bot running on your machine acts with keys that never leave your hands. That difference is the whole story.
// CUSTODY IS CONTROL
When a third party holds your funds or a withdraw-enabled key, they can move your money. Not "might in theory" — the capability is the arrangement. Every promise on top of that ("we'd never," "audited," "trustless") is asking you to trust the promise instead of the math.
// THE HONEYPOT PROBLEM
Pooled custody is a single large target. A service holding a thousand users' funds is a thousand times more worth attacking than any one of them. You don't have to be careless to lose funds in a honeypot — you just have to be in the pool when it drains.
// EXIT-SCAM RISK
An anonymous team plus a withdraw button is a standing option to disappear with the balance. Black-box logic compounds it: if you can't read what the bot does, you can't tell a strategy from a slow rug. And when it goes wrong, there is no recourse — no chargeback in the wasteland.
Their bot holds your funds. Ours holds nothing. We give you the signal — you build the weapon.
// WHY SELF-BUILD IS SAFER
- Nobody else can withdraw your funds — your keys stay on your machine, in your bot, under your control.
- You're not in anyone's honeypot — there is no pool to drain.
- You can read every line — the logic is yours; no black box, no anonymous dev.
The Forge sells the signal, never the execution. We never see your keys. The signal is data; your bot, on your hardware, decides what to do with it.
// THE HONEST COUNTERBALANCE
Self-build removes third-party trust risk — it does not remove all risk. You still own:
- Key hygiene — a leaked or mishandled key on your own machine is still a loss. Self-custody is a responsibility, not a magic shield.
- Code bugs — a bot you wrote can lose money through your own mistake. Read it, test it, size it small first.
- Risk limits — position sizing, stop conditions, and exposure caps are yours to set and enforce.
- The signal is data, not a guarantee — it describes what is, not what will happen. No edge is risk-free; no return is promised.
A project that tells you self-build is totally safe is selling the same false comfort as the custodial services it warns about. We won't. The trade-off is real: you take on your own key hygiene and code in exchange for never being in someone else's honeypot. We think that trade is worth it — and we think you should make it with your eyes open.
// SIGNAL ACCESSWe never see your keys. Neither should anyone else. No refunds in the wasteland.
