Getting started

Full walkthrough for running Latrine Bot on your Pump.fun token in the cloud dashboard. Mainnet LIVE only - no local install, no test-mode switch in the client app.

What you need before you start

• A Pump.fun token you created (or control the creator wallet for).
• The token mint address (contract address, CA).
• The dev wallet that launched the token on Pump.fun - this wallet receives creator fees and signs claim, buyback, and airdrop transactions.
• The dev wallet private key in Base58 format (64 bytes when decoded).
• A Helius Solana mainnet RPC URL with your API key in the query string (used for all on-chain calls and holder snapshots).
• Enough SOL on the dev wallet for network fees and reserves (see below).
• A Solana wallet (Phantom, Solflare, etc.) to sign in to the dashboard.

DexScreener is used automatically for market cap and price. You do not need a DexScreener API key.

Step 1 - Sign in to the dashboard

Pick any one method. Each method is a separate account (projects do not carry over between wallet, Google, and X).

Option A - Solana wallet (Phantom)

1. Open the dashboard.
2. Click Connect wallet and approve the connection.
3. Sign the Sign-In With Solana (SIWS) message to start a session.

Option B - Google

1. Click Continue with Google.
2. Approve at Google. You return to the dashboard automatically.

Option C - X

1. Click Continue with X.
2. Approve at X. You return to the dashboard automatically.

Your login (wallet, Google, or X) is only for the dashboard account. The dev wallet secret under Credentials is separate - it must be the Pump.fun launch wallet that can claim creator fees.

API details: Authentication.

Step 2 - Create a project

1. In the Controls bar, paste your Pump.fun token mint (CA) first. This field is required - you cannot create a project without it.
2. Optionally enter a project name (any label for yourself). If you leave it empty, the dashboard uses My Project.
3. Click Create. The server loads the token symbol (ticker) from DexScreener and saves it with the mint in bot settings.
4. Pick the project in the dropdown.

Each project maps to one Pump.fun token. You can run up to 25 projects per connected wallet.

The Token symbol field under Bot settings is read-only. It always follows the mint. If you change the mint later and click Apply settings, the ticker is refreshed from DexScreener automatically.

Step 3 - Get a Helius RPC URL

Latrine Bot needs a reliable mainnet RPC with DAS (Digital Asset Standard) support to list all token holders. We recommend Helius.

3a. Create a Helius account

1. Go to helius.dev and sign up.
2. Open the Dashboard and create a new project (any name).
3. Copy your API key from the project settings.

3b. Build the RPC URL

Paste this into the dashboard Helius RPC field, replacing YOUR_KEY with your real key:

https://mainnet.helius-rpc.com/?api-key=YOUR_KEY

The API key must be in the URL. The bot does not use a separate HELIUS_API_KEY field in the cloud dashboard - only the full URL is stored.

3c. Test the connection

1. Save credentials (see next step).
2. Click Test RPC. A successful test runs getHealth and getSlot against your URL.

Use mainnet only. Devnet will not work with Pump.fun creator vaults or real holder snapshots.

Step 4 - Add credentials

In the Credentials panel:

• Dev secret - Base58 private key of the wallet that created the token on Pump.fun. Must decode to exactly 64 bytes. Export from Phantom: Settings - Security - Export private key (Base58).
• Helius RPC - Full URL as above.

Click Save credentials. Secrets are encrypted at rest (AES-GCM). The full RPC URL is never shown again after save - only a masked hint.

Security: Use a dedicated dev wallet with only the SOL you need for bot operations. See Security.

Step 5 - Fund the dev wallet

The bot is self-financing per cycle: claim, buyback, and airdrop are paid from creator fees claimed in that cycle, after reserving SOL for transaction fees and ATAs.

You still need starting SOL on the dev wallet:

• At least about 0.001 SOL to attempt a claim transaction.
• At least min reserve SOL (default 0.05) left on the wallet after operations - set under Bot settings.
• Practical launch buffer: minReserveSol + minClaimSol (defaults about 0.055 SOL) plus extra headroom for busy cycles.

Step 6 - Configure bot settings

Open Bot settings and click Apply settings after changes. Main fields:

• Mint (CA) - Set at project creation; you can change it here (valid Base58 only; cannot be cleared). Required before any cycle runs.
• Token symbol - Shown read-only. Loaded from DexScreener when you save the mint. Not editable by hand.
• Cycle interval (s) - Time between cycles (5-3600, default 60).
• Min claim (SOL) - Skip claim until the Pump.fun creator vault holds at least this much (default 0.005).
• Min reserve (SOL) - SOL the bot tries to keep on the dev wallet for fees (default 0.05).
• Rewards to distribute % - Share of pooled creator fees spent on holder rewards this cycle after tx fees (default 100). Unspent share rolls forward. Changes to split, payout, or public perks are logged publicly on your token page (no opt-out). See Distribution transparency.
• Slippage (bps) - 500 = 5% (default). Applies to buyback and Jupiter swaps.
• Airdrop reward - What eligible holders receive each cycle: Project token (buyback, default), SOL, USDC, or a custom token by mint. USDC and custom tokens are bought from claimed fees via Jupiter; SOL is split directly. Holders still qualify on your token regardless of the reward. For a custom token, paste its mint in Reward mint (CA) - it must be tradable on Jupiter. Full reference: Configuration - Airdrop reward.
• Holder reward choice (optional) - Let eligible holders pick token / SOL / USDC on your token page. Toggle under Bot settings. See Holder reward choice.
• X post boost (optional) - Let anyone post on X to join the next drop: one post URL per token forever, one active claim per wallet per token per hour. Holders get a bigger slice; non-holders a small intro airdrop. Toggle under Bot settings. See X post boost.
• Min / max holder - Fallback floor and anti-whale cap in whole tokens (the number you would see on Pump.fun or in a wallet).

Hold cycles are configured per tier (not a global bot setting). Full reference: Configuration and Eligibility.

Step 7 - Set eligibility tiers

In Eligibility tiers, set MC threshold, minimum tokens, and hold cycles for each row. As market cap grows, the floor usually drops and hold cycles rise. Default tiers are pre-filled for new projects. Click + Add tier to customize, then Save tiers (separate from Apply settings).

Market cap is read from DexScreener (Pump.fun or PumpSwap pair) with a 30 second cache. No API key required.

Step 8 - Launch readiness

Before Start or Run now, open Launch readiness in the Control panel (or call GET /api/projects/:id/preflight from your own app).

1. Click Check again. Every required line must show a green check.
2. Typical fixes: wrong dev wallet (must be Pump.fun launch / claim wallet), RPC URL missing api-key, low SOL on dev wallet, mint typo.
3. Dev wallet is creator compares your saved pubkey to on-chain claim wallets (bonding-curve creator, PumpSwap coinCreator when graduated, fee-sharing admin when applicable).

API details: Preflight.

Step 9 - Start on mainnet

1. Confirm launch readiness is green.
2. Click Start for the scheduler, or Run now for a single cycle.
3. First scheduled cycle runs after about 3 seconds, then every cycleIntervalSec seconds.
4. Monitor the log for claim, buyback, and airdrop events.

Each cycle: check vault - claim fees - read market cap - snapshot holders (Helius DAS) - apply eligibility - acquire the reward asset (buyback, Jupiter swap, or none for SOL) - airdrop to eligible wallets.

Step-by-step pipeline: How it works. Modes: Modes.

Step 10 - Stream overlay (optional)

Easiest for OBS: open Stream Studio on your streaming PC, pick your token, arrange layers, and paste the OBS URL into a Browser Source. No dashboard login or API keys.

Other options: the dashboard Widget builder (per-project widgets and site embeds), or a custom overlay with a Metrics API key and your own HTML/JS.

Checklist before Start

• Launch readiness: all required checks green.
• Mint address is correct; dev wallet matches on-chain Pump.fun claim wallet.
• Helius RPC tested successfully.
• Dev wallet funded; minClaimSol and minReserveSol make sense for your fee flow.
• Tiers and hold cycles match your community rules.
• Metrics key stored safely if you embed it in a browser source URL.

Troubleshooting

• Save dev wallet and RPC credentials before running - shown if secrets are missing.
• Dev wallet is not the Pump.fun creator - use the launch wallet private key; see preflight detail for expected pubkey.
• Not ready to launch - fix Launch readiness before Start (dashboard blocks start until preflight passes).
• Invalid mint address - CA must be valid Base58 (32-byte pubkey).
• IDLE / vault below min claim - Normal until enough creator fees pool on Pump.fun.
• RPC errors - Check API key in URL, Helius quota, and mainnet URL.
• No eligible holders - Lower tiers, reduce hold cycles, or wait for holders to qualify.
• Buyback failed - Often slippage or liquidity; try adjusting slippageBps or wait for more vault SOL.

Back to documentation index