Solana — newly pooled meme-tokens via Jupiter

Trench

SI-BOT-TRENCH

Live, risk-gated Solana meme-token execution engine. Discovers newly pooled tokens, screens them through on-chain launch forensics and technicals, and sizes strictly sequential entries — one open position at a time, hard-capped bankroll.

$121 day

$11930 days

Rent 1 day Rent 30 days Ask a question first

Those links return payment terms over x402. If you would rather pay by Cash App or Chime, get in touch and include the bot and the period you want.

Specification

Market: Solana — newly pooled meme-tokens via Jupiter
Language: Rust (compiled from source)
Runs on: Your machine — Linux, macOS, or WSL
Needs: Solana RPC + WS endpoint, a dedicated wallet keypair, a Jupiter API key (recommended)
Dry run: No — there is intentionally no paper mode

What it actually does

Pulls newly created first pools from Jupiter Tokens V2, keeping up to 500 age-eligible candidates with 45 in a live price/indicator hot tier.
Requires roughly 105 seconds of price history and persistent (not single-spike) participation growth before a candidate can pass — an early-confirmation sniper, not a first-block one.
Runs launch forensics before a first entry attempt: traces the mint's creation transaction, creator allocation, signer/owner counts, and repeated use of the same funding wallet across launches, to screen out likely rugs.
Screens mint/freeze authorities and dangerous Token-2022 extensions (transfer-fee, permanent-delegate, transfer-hook, and others) directly from the mint account.
Prices every entry and exit through an executable Jupiter route before acting — rejects anything with too much price impact or projected round-trip cost.
Sizes entries strictly sequentially: exactly one open position at a time, so a new candidate is never considered while one is still open, however attractive it looks.
Manages exits on a stop, staged profit-taking with a trailing ratchet, and a max hold time, with urgent exits routed through Jito for MEV-protected delivery.
Logs every accepted and rejected candidate, so entry thresholds can be improved from evidence rather than guesswork.

The settings that decide your risk

Setting	What it does
`max_bankroll_sol / entry_sol / max_position_sol`	total strategy bankroll and per-entry size (shipped: 0.10 / 0.025 / 0.025 SOL)
`max_open_positions`	hard cap on concurrent positions — shipped config allows exactly 1
`min_sol_reserve`	wallet balance kept untouched for fees and rent (shipped: 0.03 SOL)
`max_daily_loss_pct / max_weekly_loss_pct / max_drawdown_pct`	circuit breakers that halt trading
`forensics.max_creator_initial_pct / max_creation_signers`	launch-forensics thresholds for screening likely rugs
`initial_stop_pct / trailing_stop_pct / max_hold_secs`	exit management

Credentials and safety

This bot signs Solana transactions, so it needs a full wallet keypair — a Solana keypair has no permission model, unlike an exchange API key, so there is no trade-only setting. Generate a fresh wallet, fund it with your trading budget and nothing more, and never put your main wallet in the config. The keypair is loaded only from the file named by SOLANA_KEYPAIR; it is never embedded in the config file or written to logs.

Specific risk for this bot

Sniping brand-new launches is the highest-variance activity in this market — most new tokens go to zero, and launch forensics reduces exposure to obvious rugs without detecting all of them. There is no paper-trading mode: every run is real funds from the first trade. The shipped config caps total strategy bankroll at 0.10 SOL, sends only complete 0.025 SOL entries, and allows exactly one open position at a time — verified directly against the running binary's own config output, not just the README.

It can lose money, including all of the amount you fund it with. There is no published track record and no guarantee of profit. Start small.

Getting it running

cargo build --release
export SOLANA_RPC_URL='https://your-mainnet-rpc.example'
export SOLANA_WS_URL='wss://your-mainnet-rpc.example'
export SOLANA_KEYPAIR='/absolute/path/to/dedicated-trench-keypair.json'
export JUPITER_API_KEY='jup_optional_but_recommended'
export BOT_LICENSE='...'

./target/release/trench check --config config.toml   # validate first
./target/release/trench run --config config.toml

Ships as source, built locally with cargo — same as Pump Trader (Rust). Run `cargo test`, `cargo clippy --all-targets -- -D warnings`, and `trench check` before the first live run, exactly as the bundled LIVE.md runbook recommends. A Jupiter API key is strongly recommended: discovery, metadata, prices, and executable routes create short request bursts.

Set BOT_LICENSE to the licence string you received. The bot verifies it at startup against https://saylorinnovations.com/api/license/verify and will not run without a valid one.