You hold everything. I hold nothing.

A Telegram bot that holds your keys is convenient right up until it isn't. One breach on their end, and every customer's wallet drains at once. A server sitting on thousands of private keys is the single juiciest target in crypto.

I don't have that server. There is no Gobli account system, no hosted key vault, no database, nothing of yours lives on my side, because there is no "my side." You rent a VPS, you run me on it, and your key stays in a file only you can reach. There's no honeypot to steal from, because I never built one. That's the actual security argument for self-hosting, not a privacy nicety, the whole point.

The other cost of custody

The bots that hold your keys also take a cut of every trade, forever. BonkBot charges a flat 1% on every trade. Banana Gun charges 1% on every sniped buy. I'm $199 once, and then 0%, on every trade, for as long as you run me.

I talk to a handful of outside services to do my job. But there's a hard line your private key never crosses. This is that line.

Everything in the top zone happens on your box. Only the finished, signed transaction and ordinary data requests ever leave it.

Where your key lives

Your wallet's private key lives in exactly one place: a .env file on your VPS. When I start up, I read it once (config.py), turn it into a solders.Keypair held in memory, and from then on I use it only to sign transactions locally, keypair.sign_message(...). The raw key is never sent anywhere, by me or to me. Signing happens on your machine; only the finished, signed transaction goes out.

Only you can talk to me

I'm locked to a single Telegram chat, the TELEGRAM_CHAT_ID in your .env. Every command checks that first, and any other chat is silently ignored. Telegram is a public app; this is what makes the bot yours inside it.

What a buy actually does

Paste a mint address in Telegram, and here's the exact sequence, in order, because the order is the point:

1. You paste a mint address into Telegram.
2. I ask Jupiter's aggregator for a quote and a swap transaction.
3. I ask Helius for a live priority-fee estimate (getPriorityFeeEstimate)…
4. …and simulate the transaction (getComputeUnits) to tune that fee.
5. I sign it locally with your key.
6. I send it through Helius Sender, staked, multi-region, skipping the public mempool, with a plain-RPC fallback if that path fails.
7. I poll until it confirms.
8. Concurrently, I pull liquidity, tax, holder-concentration and honeypot data from Rugcheck, GoPlus and DexScreener and print it on your receipt. (Why that runs alongside and not before the buy is in section 03.)

The Setup Wizard, you don't have to trust me on it

Getting your key into that .env file is the one genuinely scary moment, so I made it inspectable. The Setup Wizard is a single local HTML file (setup.html). Open it and view the source, Ctrl+U, it's small, and you'll see it plainly: no <script src>, no external resources, and not one network call anywhere in it. No fetch, no XMLHttpRequest, no WebSocket. The key you type only ever touches a JavaScript variable and your browser's own save-file API (showSaveFilePicker on Chromium, a plain download on Firefox and Safari). It writes the file to your disk and talks to nobody. Don't take my word for it, read it.

A page like this is worthless if it only lists strengths. Here's what I don't do, so nothing reads as a hidden gotcha later.