FAQ

Honest answers to common questions.

Where is my data stored?
On a single VPS we control. data/wallets.json (encrypted PKs) and data/activity.json (signing log) are mode 0600 — only the bot process can read them. Nothing goes to third-party clouds, no analytics SDKs, no telemetry.
What happens to my PK when I delete a wallet?
The encrypted entry is removed from data/wallets.json. Past activity-log entries are kept (so you can still audit history).
What if I see something in the activity log I didn't initiate?
Rotate the wallet immediately: delete it in /wallet, send remaining funds to a fresh address, and consider whether someone else has access to your Telegram account. Then ping the operator with what you saw.
Why does my chat message with the PK auto-delete?
To keep your private key out of your visible chat history. The bot deletes the message immediately on receipt. Best practice on top of that: paste the key from a password manager rather than typing it, and don't screenshot or back it up unencrypted.
How does the swap work?
/wallet → 🔁 Swap. Pick a direction (USDC→HYPE or HYPE→USDC), type the amount, confirm. Routed through the liqd.ag aggregator, which finds the best price across HyperEVM DEXes and handles WHYPE wrap/unwrap. Bot fee (0.50%) is skimmed by the aggregator — no extra tx.
What's the bot fee?
0.50% per trade. On buys/sells: collected as a separate USDC transfer right after the trade settles (you'll see a fee entry in the activity log). On swaps: skimmed inline by the aggregator — no separate tx.
Why is my round-trip loss bigger than just the bot fee?
alt.fun's protocol takes ~0.75% on the buy and ~0.75% on the sell (paid to the protocol, not to the bot operator). Add the bot's 0.50% per side and bonding-curve slippage and you're typically looking at 2-3% round-trip on small trades. None of that is hidden — it's just the cost of bonding-curve mechanics.
What's the dev launches badge on the Dev line?
Count of alt.fun tokens that creator has previously launched: 🆕 (1st launch) for first-timers, (3) for repeat launchers, (100+) for the rest. Useful signal — first-timers carry more rug risk; serial launchers may have a track record you can check.
Is the code open source?
Not currently. The security guarantees rely on the hardening described in Security model, not on source code disclosure.
Who runs this?
One individual operator (@lrnigger). The bot is currently single-user and not publicly open to new users.
Question not here? Ping the altDesk community.