Track record
How often the risk read is right
Every token someone checks on Trench Report is logged with the read it got at that moment, then watched for seven days. Here's what happened to each one, including every false alarm and every miss. Nothing on this page can be edited after the fact.
What counts as right and wrong
The same rules decide every token, automatically. They were fixed before any result came in, and a result can't be changed once it's recorded.
Every result
Newest first. Tap a token to open its current report.
Which warnings mattered
Check we didn't change it
Once each day ends (UTC), every read logged that day is fingerprinted with SHA-256 and the fingerprint is posted publicly on X. If anyone altered, added or back-dated a single read, the day's text would no longer produce the same fingerprint. The fingerprint covers the reads themselves; outcomes are decided later by the rules above, from public market data you can check on DexScreener.
shasum -a 256 day.txt on a Mac or Linux, or certutil -hashfile day.txt SHA256 on Windows, or paste the text into any SHA-256 tool. The result should match both the fingerprint here and the one posted on X that day.What this does and doesn't show
- Only tokens people chose to check. Not every token launched, and not a random sample. People tend to check tokens they're unsure about, which can push every number up.
- The first read only. A token is logged the first time anyone checks it here. A read that changes later (a mint authority revoked, say) doesn't change the logged one.
- Most memecoins fail whatever the read says. That's why the base rate is shown beside every number. A High risk read is only useful if High risk tokens go bad more often than tokens in general.
- Low signal risk is not "safe". It means the structural checks found nothing. A token can pass every check and still be sold into or abandoned.
- Not financial advice. This page measures a tool. It doesn't tell you what to buy or sell.