Trench Trending: Read the entry fields
Trench Trending lesson
Read the visible fields in context
Start with identity and time, then use the visible market and holder context to form a question for fresh research.
Identity and timing
Match the token identity and post time before connecting an update to an entry. Age is the reported token age, not time since it started trending.
Security summarizes the scan's alerts and callouts at that time. A green status is not a safety guarantee.
Market and holder context
Market cap is the reported value of the token supply. Liquidity is the reported liquidity amount; launchpad entries label this vLiq. Neither figure guarantees what a trade would receive.
1-hour volume is the reported amount traded in that window. The holder count reports addresses, which need not be separate people. These fields describe the entry, not the full selection rule.
Advanced field detail
- Bundles
- The displayed bundle count is followed by bought supply share and, when shown, held supply share. Bought and held describe different amounts; the labels do not establish an owner's identity or intent.
- Snipers
- The count of buyers labeled as snipers by the detector, with bought and held supply shares when supplied. The label alone does not establish who controls those addresses.
- First 20
- The earliest twenty buyers' combined bought share of supply. Any emoji-category percentages are category bought shares of total supply. A holding value is separate when shown.
- Developer
- The displayed developer SOL balance and token-supply share are different measures. A nested Sold value is the reported developer-associated sold share of token supply, not a percentage of the SOL balance.
Read only the fields present in that entry. Verify the returned token address and chain before relying on a Scan result.