The trenches, written down by the people in them.

Every model that tries to talk about this market is working from documentation that doesn't exist. This is the documentation: open to read, open to correct, and wired straight into your AI.

The wiki

Ask any AI what a bundled launch looks like on-chain. Watch it guess.

Trench knowledge is oral. It lives in replies, voice chats, streams, and group DMs, it turns over in weeks, and almost none of it is written anywhere a model can read. So the models fall back on 2021 crypto-Twitter boilerplate and get everything wrong: the mechanics, the vocabulary, the tells, the timelines.

Meanwhile the people who do know are on X, explaining it to each other for free, several hundred times a day, in threads that are unindexed and gone by Thursday.

So this is where it gets written down. People who actually trade add and alter the definitions, everyone votes on which reading is right, and the argument itself stays visible on the board instead of being resolved away. A word with three meanings keeps all three.

Read the wiki →


MCP

Point your AI at it.

The wiki is a live MCP server. Connect it once and your model looks terms up here instead of guessing, in Claude, Cursor, or anything else that speaks MCP. Read-only, no account, no key.

https://thetrenches.wiki/mcp
search_trenchesSearch every entry by word or meaning.
get_termOne term in full, with any competing readings attached.
list_termsThe whole index, filterable by category.

Claude Code, one line:

claude mcp add --transport http trenches https://thetrenches.wiki/mcp

Anything that takes a JSON config:

{ "mcpServers": { "trenches": { "type": "http", "url": "https://thetrenches.wiki/mcp" } } }

The same data is plain JSON at /api/entries if you'd rather skip MCP, and robots.txt allows every AI crawler on purpose. The point is that models can read this.


Tokenomics

A coin, and a wiki that doesn't depend on it.

There's a pump.fun coin for this wiki. It has no allocation, no presale and no vesting, and it buys you nothing here. The wiki is free to read and the MCP server is free to call, whatever the chart does.

Creator fees go to the desk and fund the project. Hosting and the X API bill are real and they come out of somewhere. Nothing on this page is a promise of a return.

What exists from the first entry onward is the contribution log: every entry, every correction, every dispute, attributed to the handle that wrote it and timestamped. Whatever this turns into, that record is already written and it isn't editable after the fact.

contract2PeBgfWnC8zGmkhLjaEa2LvLmz57Ce12vGWj9rYJpump

Contribute

Reply to the bot. That's the whole process.

Two commands. Each one is a reply to @thetrencheswiki on X. No account here, no email, no site login. The bot answers every one it accepts, so you always know whether it landed.

Add a definition. Term on the first line, what it means underneath.

@thetrencheswiki define: bundle buying your own supply in the same block as the launch, across wallets you control. standard on solana. what people argue about is the size of it, not whether it happened.

It replies: added to the wiki. you're on it as the source.

Disagree with one. Nothing gets deleted. Both readings stay up, marked.

@thetrencheswiki dispute: bonded bonded and migrated get used interchangeably but they aren't the same moment. bonded is the curve filling. migrated is the pool actually opening, and there's a gap between them.

It replies: logged as a competing reading. both stay up.