Axiom walkthrough
A walkthrough using Trench.Tools on Axiom.
A high-level look at how Trench.Tools runs — the pieces, the setup flow, what it costs, and how fast it executes. Detailed setup steps live in the docs.
A three-minute, unedited walkthrough of trades, deploys and snipes running through a self-hosted Trench.Tools stack.
A walkthrough using Trench.Tools on Axiom.
A walkthrough using Trench.Tools on J7Tracker.
Three components, all running locally on your machine or VPS. Your wallets, keys and execution stay on the host you control.
Local Rust trading host. Owns your wallets, presets, routes and the trade build/sign/send path.
Launchpad workflows: deploy, vamp, snipe, dev-buy, dev-sell and follow flows for Pump, Bonk and Bagsapp.
Injects Trench.Tools into the terminals you already use, and routes every trade through your local engine.
Most users on a fresh VPS get the stack live in about five minutes. The full setup walkthrough — commands, environment variables, SSH tunnels — lives in the docs.
Pick a host: a local PC or a cheap VPS near your provider endpoints. One command starts the execution engine and LaunchDeck on loopback ports.
Load the extension folder in Chrome or Edge in developer mode, then paste the auth token your engine writes out on first start.
Quick-buy controls and panels appear inside supported terminals. LaunchDeck runs alongside, embedded in the extension or as a standalone UI.
You replace a percentage of every trade with a flat monthly bill. At a 1% platform fee, $80/month of infra breaks even at just $8k of monthly trading volume — well under an hour of active trading for most users.
Click to sender accept, on a Helius Developer tier RPC plus integrated private relay providers. Real numbers depend on region, RPC tier and route — benchmark your own setup.
Wallets, keys and execution stay on your machine or VPS. Browser-facing routes are auth-gated, and remote access uses an SSH tunnel — no raw ports exposed to the public internet.
Full security model and threat boundary are documented in
SECURITY.md. Read it before running with real wallets.
You need the open-source repo, a machine or VPS to run the local engine, a browser extension, and your chosen Solana RPC/send providers.
No. The stack is local-first. Wallets, keys and execution stay on the host you control instead of being routed through a fee-taking platform account.
Yes. Trench.Tools actively supports Axiom, J7Tracker and X, with the browser extension connecting supported pages to your own backend.
Self-hosting removes recurring percentage platform fees, keeps sensitive execution under your control, and lets you configure providers, routes, wallets and presets directly.