Trenches Explained: New, Almost Bonded, Recently Bonded

Trenches is Padre Terminal's dedicated view for tokens still on a bonding curve — the earliest, most volatile stage of a token's life, before it migrates to a standard liquidity pool. It's a different tool than New Pairs or Trending, built specifically for this pre-migration window.

The three columns, explained

• New — tokens that just launched and are early in the bonding curve. Highest volume of listings, lowest signal-to-noise ratio.
• Almost Bonded — tokens nearing the end of their bonding curve, which is often where activity concentrates as the migration point approaches.
• Recently Bonded — tokens that have just finished bonding and migrated to a full liquidity pool.

What each token card actually shows

Beyond price and basic stats, Trenches surfaces data specifically useful for assessing a pre-migration token:

• Top 10 holder concentration — the percentage of supply held by the largest wallets, excluding pool/bonding-curve addresses.
• Dev holding — how much of the supply the token's deployer wallet holds.
• Bundle detection — flags trades executed in the same slot in the same direction, which can indicate coordinated buying rather than organic demand.
• Dex Paid / Dex Boosted indicators — whether the token creator paid for enhanced listing info on Dexscreener, which is a marketing signal, not a safety one.

Filtering effectively

Trenches supports saved filters with min/max ranges across its metrics. Rather than scrolling the full unfiltered New column, setting a minimum liquidity threshold and a maximum top-10-holder percentage narrows the list to tokens that at least clear a basic structural bar — see our safety checklist for the reasoning behind those specific thresholds.

Why "bundled" flags stop after migration

Same-slot trade detection is only meaningful pre-migration, when a small number of wallets can realistically coordinate trades against a thin bonding curve. Once a token migrates to a full pool, trading volume and participant count typically increase enough that same-slot clustering becomes a much weaker signal — which is why the terminal stops flagging it at that point rather than showing misleading noise.