Trenchora documentation

Introduction

Trenchora runs in your browser and signs everything through your own wallet. Launch has three paths: a pump.fun launch (token on the bonding curve plus your own buy), a standard SPL or Token-2022 token (your own supply, minted to your wallet), and a Raydium liquidity pool for a token you hold. Around that: a vault of sub-wallets only you can decrypt, analytics, airdrops, a Volume Engine and Exit tooling. Unfinished launch forms are saved as drafts on your account. There are two plans: Free (no upfront cost; a 0.1 SOL platform fee inside each launch) and Pro ($199 per 30 days or $1,499 lifetime at list price, paid in SOL at the live price; no platform fees and every pro tool).

Everything described here is live. Anything still being built is not in the terminal and not in these pages.

Prerequisites

• A Solana wallet that supports the Wallet Standard (Phantom, Solflare, Backpack and others).
• Enough SOL for the platform fee, account rent and the network fee. The exact amounts are shown before you sign.

What the server can see

• Your wallet address and the signatures of transactions you make here, so they can be listed on your Overview.
• Your sub-wallets' public addresses and an encrypted blob it cannot decrypt. The encryption key is derived in your browser from a signature only your main wallet can produce.
• Token images and metadata you upload, which are served publicly at the on-chain metadata URI.
• Your settings, including a custom RPC endpoint if you set one; it is used by the server only to relay your own requests.
• Never: a seed phrase, a private key, or a transaction you did not sign in your wallet.

Fees and failures

The platform fee is a transfer inside the same transaction as the action it pays for, so a transaction that fails charges nothing. Account rent and network fees go to the Solana network. Every transaction is simulated before your wallet opens; a simulation error is shown in plain language and nothing is sent. Once sent, each stage (submitted, confirming, confirmed or failed) is shown with the signature linked to an explorer.

Launches and pools

pump.fun. Launch → pump.fun launch creates the token on pump.fun's bonding curve and buys from your wallet in the same transaction. On Pro you can add buys from your unlocked sub-wallets. The preview reads the curve parameters from the chain and prices every buy in order, so the tokens each wallet receives and the bundled share of supply are known before you sign; the share is labelled with the thresholds that scanners such as Bubblemaps use. On mainnet, a launch with sub-wallets is sent to Jito as one bundle, so the creation and all buys land in the same block or not at all; a bundle that does not land charges nothing. Devnet has no block engine, so there the transactions are sent one after another. Every transaction is confirmed individually; the page never reports success from a bundle id alone.

Raydium. Launch → Liquidity pool opens a constant-product pool (CPMM) of a token you hold against SOL. The fee tier is read from Raydium's on-chain configuration, an existing pool for the pair is detected before you sign, and after creation you can burn all LP tokens in one irreversible transaction, which is what makes liquidity permanent. On Free the 0.1 SOL platform fee is part of the pool transaction; on Pro there is none. Raydium's creation fee and the pool accounts' rent are shown in the preview.

Volume Engine

The Volume Engine (Pro) runs buy and sell cycles for one token from your unlocked sub-wallets. It finds the token's market on the chain (an open pump.fun curve, or a Raydium CPMM pool against SOL), then trades one at a time: each trade is quoted from the live market, simulated, signed by the sub-wallet that trades, sent, and confirmed before the next one is scheduled. Sizes and delays are drawn from the ranges you set. The log lists every signature, and amounts come from each confirmed transaction's balance changes rather than from quotes.

It runs only in your browser tab: keys never leave it, trading pauses while the tab is hidden and stops when it closes, and Stop waits for the in-flight transaction to confirm or fail. Every trade costs network fees and the venue's trading fee, so a buy-sell cycle ends with less SOL than it started with. Creating volume with wallets you control may breach a venue's terms or the law where you are; the page asks you to acknowledge that before starting, and Trenchora records your trades under your account so you can see what was spent.

Analytics

Analytics reads a token from the chain: supply and authorities, the largest holders summed per owner, the share the top ten hold, the holder count where the RPC allows a full scan, and the last signatures that touched the mint. Your own share is computed in your browser from your wallet and your unlocked sub-wallets, and those owners are marked in the holder list. Chain reads are cached for up to a minute and the page shows when they were made.

Price, volume and liquidity come from DexScreener, are fetched by the server, cached with a timestamp and always labelled as third-party; DexScreener indexes mainnet only. The transactions table lists what you did through Trenchora (deployments, pass payments, volume trades) for a time range you choose, with a CSV export.

Notifications

Settings can deliver a message when a deployment, launch, pool, airdrop, volume run or exit finishes or fails: to an HTTPS webhook you run (JSON body, signed with an x-trenchora-signature HMAC-SHA256 header using a secret shown in Settings) and/or to a Telegram chat through your own bot. Delivery happens from the server; the browser reports the result and the server posts to your destinations only. Webhooks to local or private addresses are refused, and "Send a test" shows exactly what each destination answered.

Exit

Exit (Pro) sells every selected sub-wallet's whole balance of one token on its live market, either back to back or spread over random delays, one transaction per wallet signed by that wallet. The review step quotes each sale at the current price before anything is signed; because each sale moves the price, later sales receive less. Every signature is listed as it confirms, the SOL received is read from the transaction, and the sales are recorded under your account. Afterwards, one action sweeps all SOL back to your wallet and closes the empty token accounts for their rent.