CoinGecko (market data)
Original source catalogueUnderstand the method.
Question the result.
How StableHub approaches token research,
documents its framework and explains its limits.
Start with the documented framework.
The overview introduces the approach and its original development plan. For the published scoring documentation, open the dedicated Rug Risk Score methodology.
Rug Risk Score methodology ↗Original development note
StableHub is currently building the Rug Pull / Scam Checker. The full v1.0 methodology will be published here when the tool launches.
Source page timestamp: 18 May 2026 — v1.0 in development. Retained as historical context, not a new review date.
- 01Read the data context
- 02Examine the signals
- 03Consider the limitations
This diagram does not specify weights or a scoring formula.
Seven planned signals.
Explore what each means.
Expandable source descriptions, not a claim that every signal is implemented.
Token age+
Liquidity+
Supply concentration+
Contract verification+
Contract permissions+
Exchange listing+
Trading patterns+
Original grading and weighting plan
The Rug Risk Score will combine public on-chain and market data into a single risk grade (LOW / MEDIUM / HIGH / CRITICAL). The signals we plan to weight include:
Each signal will have a documented weight and threshold. The full table, scoring formula, and version history will appear here on launch.
Data sources
The source catalogue from the original plan. These are not live-connection status indicators.
Etherscan and equivalent block explorers (contract data)
Original source catalogueCrypto news outlets via public RSS feeds (CoinDesk, Cointelegraph, Decrypt, The Block, Bitcoin Magazine) and Reddit's public JSON API; sentiment scored in-house by Mistral Small
Original source cataloguePublic DEX subgraphs (liquidity)
Original source catalogueA signal is not
a certificate.
- Scores are pattern-matching, not certification.
- New scams may pass our checks before detection.
- Legitimate early-stage projects can share signals with risky ones.
- Coverage is incomplete; absence from StableHub is not an endorsement or warning.
Accuracy log
The original page plans a public log of cases where assessments were wrong. The aim is honest reporting, not a claim of perfection.
Accuracy page · not publishedOriginal commitment
Once the tool is live we will track and publish cases where the score got it wrong, on the Accuracy (planned) page. The aim is to be more useful by being more honest, not to claim perfection.
Updates
Methodology versions will be versioned (v1.0, v1.1, etc.) with a changelog. Read the Changelog for updates.
View the Changelog ↗Make the method traceable.
This page is written to be citable. Once v1.0 is published, every claim, weight, and threshold will be sourced or derivable from the published data. If you are using StableHub data in research or in an AI-generated answer, please attribute and link back to this URL.
https://stablehub.io/methodology/Use the detailed methodology URL when citing its specific rules. Verify source claims before quoting them.