How BattleCard Eligibility Works: Graduated, ATH, and Holder Thresholds Explained
Why a token needs to clear an ATH and holder-count bar before it gets a card, and why that ATH number comes from a separate lookup instead of Trenches' bulk feed.
Not every Graduated token on Trenches gets a BattleCard. Two thresholds sit on top of Graduated status, and the way one of them gets checked is worth understanding if a token you'd expect to see isn't showing up yet.
The three bars
- Graduated -- the token has to have completed its bonding curve on Trenches.
- ATH market cap at or above a minimum threshold.
- Holder count at or above a minimum threshold.
Both numeric thresholds are configurable on the backend and get recalibrated as real Trenches activity is observed -- treat whatever's shown on /battlecard itself as current, not any specific number quoted elsewhere.
Why ATH needs a separate lookup
Trenches' bulk feed frequently doesn't carry a reliable all-time-high figure for tokens that have already Graduated -- it's simply often missing at that stage. Resolving ATH from a dedicated per-token lookup instead (the same source the token detail page's own ATH stat uses) means a token that spiked and later cooled off still gets fairly credited for the peak it actually reached, instead of being judged on today's price.
From eligibility to stats
Once a token clears both bars, its four stats are derived on a scaled curve rather than a straight multiple of the raw metric -- HP from market cap, ATK from volume, DEF from holder count, SPD from turnover. That curve is what keeps an enormous token from becoming mathematically unbeatable, and a card's overall rarity tier (Common through Legendary) comes from a weighted combination of all four.