dlmmbot

For AI agents ​

You are installing DLMM Bot for a human operator. Prefer the Easy (Railway) path unless they already have a VPS and ask for Advanced.

llms.txtllms-full.txtEasy setup

Read these first ​

  1. https://dlmmbot.com/llms.txt — short map (URLs + product facts)
  2. https://dlmmbot.com/llms-full.txt — fuller summary
  3. This page + Easy setup
  4. Terms & risk waiver — human must accept in the dashboard; software is as-is, they can lose 100%

Do not invent env vars, weaken live gates, commit secrets, or put a main wallet into the bot.

Human paste prompt (optional) ​

If the human only gives you a short message, ask them to paste this (or treat it as your standing brief):

text
Install DLMM Bot for me on Railway (easy path).

Read https://dlmmbot.com/llms.txt and https://dlmmbot.com/llms-full.txt,
then follow https://dlmmbot.com/setup/agents and https://dlmmbot.com/setup/easy.

Rules: paper mode first, burner wallet only, never commit .env or keys,
require Terms acceptance in the dashboard, do not flip live unless I explicitly ask.
Tell me every URL and secret I must create myself (Railway, Helius, Jupiter).

Goal ​

A running paper farmer + public HTTPS dashboard where the human finishes secrets in the setup wizard.

Live mode is out of scope unless they explicitly ask — and then both FARMER_MODE=live and [exec] mode = "live" are required.

Hard rules ​

DoDon't
Paper firstFlip live without an explicit ask
Burner wallet onlyImport their main / cold wallet
Volume at /app/data on Railway (+ Add → Volume → mount path)Let Settings wipe on redeploy (no volume / wrong path like /data)
Keep keys in the dashboard / volumeCommit .env, keys, or DASH_TOKEN to git
One bot process per wallet/DBRun two farmers against the same wallet
Point them at TermsSkip or auto-click Terms for them without disclosure

Canonical steps: Easy setup. Summary:

  1. Fork — human forks CryptoGnome/dlmmbot (Railway only deploys repos they can access).
  2. Railway — railway.com?referralCode=SCj9lN → New Project → Deploy from GitHub → their fork. One service. Build/start come from railway.toml.
  3. Volume (required) — on the Railway project canvas: + Add → Volume → attach to the bot service → Mount path = /app/data (not /data). Redeploy. Logs must show volume mount=/app/data, not no volume detected.
  4. Domain — open the service → Settings → Networking → Generate domain.
  5. Dash token — set Railway variable DASH_TOKEN to a long random secret (≥24 chars). Easiest: open Easy setup and use the Generate / Copy buttons (browser-side), or a password-manager generator. Open https://<domain>/?token=…. Do not copy tokens from deploy logs (only a prefix is printed).
  6. Wizard — human accepts Terms; only paste RPC/Jupiter/GMGN if not already set as Railway variables (wizard detects env and skips those). Create/import an encrypted burner, stay on paper. Finish leaves Engine OFF — human flips ON in the header when ready.

Secrets the human must create ​

KeyRequiredWhere
RPC_URLYesHelius mainnet HTTPS URL
JUPITER_API_KEYBefore live (get it in paper too)Jupiter Portal
GMGN_API_KEYOptionalgmgn.ai/ai — API keys
Burner walletFor live (paper can wait)Dashboard wizard — create or Phantom import

Full signup steps: API keys.

Advanced path (only if asked) ​

Advanced setup: Node 20+, clone CryptoGnome/dlmmbot, npm install, data/config.toml + data/.env, npm run run / PM2. Suggested VPS: Vultr (~2 vCPU / 4 GB / 80 GB / Ubuntu 24.04).

After install — verify ​

  • Dashboard loads with the token
  • Terms accepted (wizard or TermsGate)
  • Mode shows PAPER
  • Heartbeat / farmer process healthy after first ticks
  • Wiki / Settings open without errors

Useful ops: Dashboard guide, CLI (status, halt, pause), FAQ.

Going live (only if explicitly requested) ​

  1. Create or import a burner in the dashboard (wizard or Settings → Wallet & secrets); never a main wallet
  2. Fund that public address with SOL (start small; leave reserve for rent — see Risk)
  3. Unlock the wallet (or set WALLET_PASSPHRASE on Railway)
  4. Paper looked sane; Helius + Jupiter set
  5. Set both FARMER_MODE=live and [exec] mode = "live"
  6. Restart / redeploy
  7. One process per wallet

Details: Easy → Going live. Usage fee on live wins: Fees.

Machine-readable indexes ​

FileUse
llms.txtLink map + one-liners — start here
llms-full.txtLonger product / deploy / safety summary

Repo mirrors: llms.txt, llms-full.txt.

llms.txt short agent mapllms-full.txt full agent summaryEasy — Railway preferred installAPI keys Helius, Jupiter, GMGNTerms & waiver required in dashboardAdvanced local / VPS / PM2Dashboard wizard, HALT, SettingsGitHub CryptoGnome/dlmmbot

DLMM Bot