Terminal Trenches Mode: The Filters, Alerts and Safety Signals

Trenches mode is Terminal's live feed of memecoins as they are launched, and it is the surface the rest of the app is built around. It splits new bonding-curve tokens into three columns: New for raw launch flow, Almost Bonded for tokens approaching graduation, and Recently Bonded for the ones that made it. Across those columns you can save filter sets on market cap, volume, top-10 holder concentration, insider holding, bonding progress, dev holding and token age, toggle roughly 19 metrics on each token card, attach a sound alert to any filter, and blacklist up to 200 developer addresses so a serial launcher never reaches your feed twice. The safety panel is the part that earns its keep: bundle percentage, dev holding, insider holding, dev funding source, fresh-wallet buys and bot detection. The feed pulls launches from pump.fun, Four.meme, Trench, Flap, Virtuals, Circus and Hood.fun, all of them independent launchpads built and run by teams unrelated to Terminal.

It is built for traders working the earliest minutes of a token's life, where there is no chart to read and the only things to judge are who deployed it and how the supply was split at birth.

The production bundle references Trenches 408 times, more than any other feature, and once you have used it for an hour it is obvious why: this is where the product's opinion about what trading looks like lives.

It is also the surface where the honest framing matters most. Only a small share of bonding-curve tokens ever graduate, and most new launches are worthless within days.

We are not putting a percentage on either statement, because the figures circulating for both come without a source we can check, and a number you cannot trace is worse than no number.

No feed, no filter set and no safety panel changes the base rate anyway. What good filtering does is cut down how many obvious traps you personally walk into, which is a smaller claim than most tools make.

What do the three Trenches columns show?

Trenches splits into New, Almost Bonded and Recently Bonded, and each column is a different game.

New is raw launch flow. Almost nothing here survives. This column is where the safety signals earn their keep, because a token twenty seconds old has no chart, no volume history, and nothing to judge except who deployed it and how the supply was distributed at birth.

Almost Bonded is tokens approaching the end of the bonding curve. There is real information here: enough buy pressure has accumulated to push a token most of the way up the curve, and holder counts and volume have started to mean something. It is also the most crowded column, because everyone else can see the same progress bar.

Recently Bonded is post-migration. The token now trades on a real pool, and the crowd that only buys graduated tokens has arrived. Note that bundle analysis stops updating at migration, so the risk read you would have used in the first two columns is partly gone here.

Enlarge

One thing to know if you followed an old documentation link: there is no /new-pairs route in the current app despite the docs pointing at one. Trenches replaced it.

Which launchpads feed the Trenches feed?

The archived documentation lists two sources: pump.fun and Four.meme. The venue list in the production bundle is longer. Trenches also reads launches from Trench, Flap, Virtuals, Circus and Hood.fun.

Worth being precise about what that means. Every one of those is an independent launchpad, built and operated by a team unrelated to Terminal. Terminal pulls their launches into a feed and gives you filters over it.

It does not run them, vet them or endorse them. Responsibility for what gets deployed on any of them sits with the launchpad and the deployer, not with the terminal you happen to be watching from.

Hood.fun is the interesting entry, because it sits on Robinhood Chain, which has an explorer entry, quote tokens and a chain color inside Terminal and appears in none of the marketing or documentation.

We have not found a public statement from Robinhood about the arrangement and are not going to characterize one. The observable part is that the chain selector ships five networks while the marketing claims four.

Which Trenches filters actually matter?

This is where the time investment pays off. Filters are saved as named presets, so you build a thesis once and reuse it. The full set of numeric ranges available:

Plus three toggles that are simple and do a lot of work: Dex paid, has socials, and dev still holding.

Dex paid means someone spent money on a DEX Screener listing upgrade, which is weak evidence of intent but real evidence that somebody was willing to spend. Has socials filters out the completely anonymous launches.

Dev still holding is the one I would think hardest about, because it cuts both ways: a deployer holding nothing has already exited, and a deployer holding a lot can exit whenever they want.

Card metrics and display options

Around 19 metrics and display options can be toggled on and off per token card. Because Terminal's interface is extremely dense already (24 pixel row heights, tabular mono numerals, 12 to 13 pixel body text), turning everything on produces a wall you cannot scan.

The version I would build: keep market cap, age, holder count, top-10 concentration, dev holding and the volume figure. Everything else goes off.

The point of a feed is that your eye catches an anomaly in under a second, and that only happens when there are few enough numbers per card for a pattern to exist.

Sound alerts

Attach a sound to a filter and Trenches makes a noise when something matches. The available sounds are a real enum in the code, and the list is exactly as unserious as it looks: CORK, RING, BELL, NICE, YEAH BOY, KACHING, UGH and CUSTOM.

CUSTOM is the one that matters. Distinct sounds mapped to distinct filters is the only way this scales, because a single alert tone across three saved filters tells you nothing except that something happened. Map your tightest filter to something you would never confuse with anything else, and leave your loose exploratory filters silent.

Small warning from experience with any alert system: the noise trains you. If your alert fires forty times an hour, you stop hearing it inside a day and the feature is worse than useless because you now believe you have coverage you do not have.

Sound is not the only channel Terminal makes noise on. The Mayhem lobbies and their voice chat are a separate surface again, where the alert is another trader talking rather than a tone.

What does the dev blacklist do?

Up to 200 addresses. Blacklisted deployers disappear from your feed.

Two hundred is a small number against the volume of new launches, and serial deployers rotate wallets constantly, so the list is nowhere near a comprehensive defense.

What it is good for is memory. The deployer who rugged you personally, the one whose naming convention you have now seen four times, the wallet you traced from a funding check.

Those go on the list and stay off your screen forever, which is worth more than it sounds when you are scanning fast and tired.

What does each safety signal tell you?

This is the part of Trenches that justifies using it over just watching pump.fun's own site. Each signal answers a narrow question, and knowing which question is the difference between a filter and a superstition.

Bundle analysis

Shows how much of the supply was acquired in the same transaction bundle as the launch, which is supply bought before anyone outside that bundle could place a bid.

A high bundled percentage means a large block of supply sits in wallets that all got in at effectively the same near-zero cost and can exit at any price above it. It is the strongest single pre-migration risk signal in the product.

It has limits. Bundle analysis is Solana only, and it stops at Raydium migration, so in the Recently Bonded column you are working without it.

Dev holding percentage

How much the deployer kept. Both extremes are informative. Near zero often means they have already sold, and the question becomes who bought. A large retained share means the largest possible seller is still loaded and has not moved yet.

There is no good number here, which is why this signal only works alongside the others. Read it together with dev funding and bundle percentage rather than on its own.

Insider holding percentage

Supply concentrated in wallets Terminal has associated with the launch, which is a wider net than the deployer address alone. It catches the pattern where a deployer holds almost nothing while five wallets funded from the same source hold 40 percent between them.

The observable effect of that shape is a clean-looking dev holding number sitting on top of supply that is still concentrated. Why any particular launch is arranged that way is not something anyone outside it can see.

Dev funding source and timing

Where the deployer's wallet got its SOL, and when. This is the most underrated signal in the panel.

A deployer wallet funded twenty minutes before launch, directly from a centralized exchange withdrawal, with no other history, is a wallet created for this launch. A wallet funded from another deployer wallet you have seen before is a serial operator, which the blacklist exists for.

Funding history is hard for a deployer to fake because it is a chain of real transactions with real timestamps.

Fresh wallet buys

Counts buyers whose wallets are new and have no meaningful history. A launch where most of the early volume comes from wallets created the same day is showing you activity, not demand.

Solana only, like most of this panel.

Bot transaction detection

Terminal flags transactions it recognizes as coming from trading bots, naming Maestro and Photon among them. Bot flow is not automatically bad, plenty of ordinary traders route through bots.

What it tells you is who you are trading against and how fast they are. A launch that is overwhelmingly bot flow is a market where your click speed is the product being sold.

Avatar reused

Flags a token whose image has been used by a previous token. Cheap to check, and it catches the laziest category of repeat scammer, the one recycling the same asset pack across launches.

Not conclusive on its own, since plenty of legitimate tokens use stock imagery, but combined with a fresh deployer wallet it is close to a decision.

Liquidity lock icon

Indicates whether pool liquidity is locked. Unlocked liquidity on a migrated token means it can be pulled. This is a straightforward binary and it matters most in the Recently Bonded column, where bundle analysis has gone dark.

Freeze authority warning

Flags tokens where the freeze authority has not been revoked, meaning the token's authority can freeze your account and prevent you from selling. Terminal has a specific error string for this outcome: "The developer of {token} froze your account, preventing you from trading this token."

That string exists in the shipped app because it happens. This is the one signal on the list I would treat as an automatic no rather than a data point, since the downside is not a bad price, it is a position you cannot exit at any price.

Token tax display

Shows buy and sell taxes on the contract. Common on EVM tokens, and the number to watch is the asymmetry: a 5 percent buy tax with a 40 percent sell tax is a honeypot with extra steps.

On EVM chains the app also surfaces a check from honeypot.is, a third-party service, and an EVA Audit AI contract check covering Ethereum and Base only. Both are outside providers whose results Terminal displays rather than analysis Terminal performs.

How do you set Trenches up?

That fourth step is not a throwaway. It is the single most costly setting on the platform for anyone trading small size, and the full write-up is here: why small trades lose money on Terminal.

What will Trenches not do for you?

It will not find you a winner. Graduation is rare and most tokens are finished within days, so the base rate is doing far more work than any filter you can build.

Discovery tools sell the feeling of an edge, and the honest version of the pitch is narrower: Trenches makes it fast to reject things, and rejection at speed is worth a lot when the feed never stops moving.

It also does not replace an exit plan. Getting in early on something that runs is only half of it, and the reason people give back gains is that they had no structure for selling.

Terminal is unusually well equipped there, with position-sized take-profits and up to five exit conditions attached at entry, and that is covered in full in our order types and exit strategies guide.

Also worth pricing in: Terminal charges a flat 1 percent trading fee with no volume tiers, stacked on top of pump.fun's own 1.25 percent bonding-curve fee, which is a lot of friction when you are taking many small shots at low-cap tokens.

Terminal rates and fees shows how that compounds. And the cashback rate on those fees is set permanently at signup, which the referral page explains.

The bottom line

Trenches is the best reason to use Terminal, and the safety panel is better than what most competing feeds show you, particularly the funding-source and bundle checks.

If you are comparing against the platform taking the most share right now, our Terminal vs Axiom comparison covers execution speed, which is where Terminal draws its most consistent criticism.

Use the feed to throw things out. Keep the filter set small enough that you actually read the results. And do not confuse a token that passed your filters with a token that is going to work, because a filter can only tell you what it did not find.

You can open the feed at terminal.pump.fun, and if you want the background on who runs the platform and how it got here, start with what Terminal is.

Where do the numbers on this page come from?

Terminal has no live official documentation. The Padre GitBook went offline in spring 2026 and every path on it now redirects to a sign-in screen, so the strongest evidence available for how the app behaves is the app itself.

The feature counts, filter fields, card metrics, sound alert names, blacklist ceiling and safety-panel signals on this page were all read directly from Terminal's live production JavaScript bundle on 6 August 2026, roughly 4.5 MB of code served from trade.padre.gg. That is first-hand provenance rather than a citation, and it is stronger than a document, but it has one limit worth stating: a bundle shows what is shipped, not necessarily what is enabled for every account.

The 1 percent Terminal fee comes from the same reading, as a fee constant of 100 basis points with no volume tier schedule anywhere in the code. The 1.25 percent bonding-curve fee underneath it is not ours to measure; it is published by pump.fun on its own fee page, which is the only official fee documentation still online, checked 6 August 2026.

Where this page declines to give a figure, that is deliberate. We do not put a percentage on how many bonding-curve tokens graduate, or on how many launches end worthless, because the numbers circulating for both trace back to no source we can check. A number you cannot trace is worse than no number. Our methodology explains how these tiers are weighted when they disagree, which they do often.

Cite this page

Every heading on this page has a stable anchor, so you can link to the exact section a figure sits in rather than to the page as a whole. A clean markdown copy is served at https://terminalpedia.com/guides/trading/terminal-trenches-guide.md.

Plain text

Copy

Concept211. "Terminal Trenches Mode: The Filters, Alerts and Safety Signals." Terminalpedia, published 6 August 2026, updated 6 August 2026. https://terminalpedia.com/guides/trading/terminal-trenches-guide

HTML link

Copy

<a href="https://terminalpedia.com/guides/trading/terminal-trenches-guide">Terminal Trenches Mode: The Filters, Alerts and Safety Signals</a>, Terminalpedia (updated 6 August 2026)

Trenches filter table, HTML

Copy

<table> <caption>Numeric filters available in Terminal Trenches, read from the production bundle on 6 August 2026 (source: Terminalpedia)</caption> <tr><th>Filter</th><th>What you would use it for</th></tr> <tr><td>Market cap</td><td>The crudest cut. Floors out sub-$5k noise, ceilings out anything already run up</td></tr> <tr><td>Volume</td><td>Separates tokens with actual trading from tokens with a deployer and a bot</td></tr> <tr><td>Top 10 holders %</td><td>Concentration check. High means a handful of wallets can end the token</td></tr> <tr><td>Insider holding %</td><td>Supply held by wallets linked to the launch</td></tr> <tr><td>Bonding progress %</td><td>The core filter for the Almost Bonded column</td></tr> <tr><td>Buys / sells</td><td>Ratio and raw counts. A high buy count with almost no sells early is often synthetic</td></tr> <tr><td>Dev bonded</td><td>Whether the deployer has previously taken a token to graduation</td></tr> <tr><td>Token age (minutes)</td><td>Precise enough to build a narrow window, like 3 to 12 minutes old</td></tr> <tr><td>Total holders</td><td>Distribution proxy. Ten holders and a $40k cap is not a market</td></tr> <tr><td>Dev holding %</td><td>How much the deployer kept</td></tr> </table> <p>Source: <a href="https://terminalpedia.com/guides/trading/terminal-trenches-guide">Terminal Trenches Mode</a>, Terminalpedia (updated 6 August 2026)</p>

Where the figures came from. One tier, and the page says so throughout. The three columns, the launchpad list, every numeric filter and toggle, the card metrics, the sound alert names, the 200-address blacklist ceiling and all nine safety-panel signals were read directly from Terminal's live production JavaScript bundle, which is first-hand evidence of what the application ships rather than a citation of someone else's reading. The 1 percent Terminal fee comes from the same reading, as a fee constant of 100 basis points with no volume tier schedule anywhere in the code. The 1.25 percent bonding-curve fee underneath it is pump.fun's own published figure, linked at the point it is used. Where a percentage circulates widely but traces to no checkable source, this page declines to publish it rather than repeating it.

Sample and window. One reading of the full production bundle, roughly 4.5 MB of JavaScript served from trade.padre.gg, on 6 August 2026. A bundle shows what is shipped, not necessarily what is enabled for a given account. Last updated 6 August 2026; first published 6 August 2026.

Reuse. You may republish these figures with attribution and a link to https://terminalpedia.com/guides/trading/terminal-trenches-guide. Please carry the date with the number: several of these are read from a shipped application build rather than from a published document, so they describe that build rather than every future release.