Reported Token-Risk Registry - Complete Guide
Version 1.1 | March 2026
Welcome to the Reported Token-Risk Registry
The SiCierto registry is a community reference for reported token-risk entries from community submissions and Rug Pull Hunter gameplay. Entries are observations or game-derived signals, not verified findings of fraud, rug pulls, or token safety. DexScreener search results are current third-party market-listing information, not complete on-chain analysis.
1. Overview
1.1 What is the Token-Risk Registry?
The registry is a searchable, public database of reported token-risk entries. It serves as:
- A research starting point before interacting with a token
- An educational reference for common warning signs
- A record of community submissions and game-derived signals
An entry is not a verified scam or rug-pull finding. A text query result is not proof of token identity or safety.
1.2 Key Features
| Feature | Description |
|---|---|
| Third-Party Market-Listing Search | Search current market-listing information supplied by DexScreener |
| 14 Supported Blockchains | Coverage across the chains currently available in the registry interface |
| Reported Signal Display | Color-coded presentation of a recorded score or concern label, not a verified verdict |
| Warning-Sign Details | Recorded observations or game-derived signals associated with an entry |
| Community Submissions | Submit a token-risk observation with supporting details |
| Game-Derived Reports | Gameplay can contribute records under its existing reporting flow |
1.3 Access
Navigate to /rug-pulls on the SiCierto platform. This guide is available at /docs/rug-pull-registry.
2. Supported Blockchains
The registry interface currently supports entries across these 14 blockchains:
| Blockchain | Symbol |
|---|---|
| Solana | SOL |
| Ethereum | ETH |
| BNB Chain (BSC) | BNB |
| Tron | TRX |
| Polygon | MATIC |
| Avalanche | AVAX |
| Arbitrum | ARB |
| Base | BASE |
| Optimism | OP |
| Fantom | FTM |
| Near | NEAR |
| Sui | SUI |
| Aptos | APT |
| Cosmos | ATOM |
Supported-chain coverage is not exhaustive within any chain.
3. Reported Signal Score System
3.1 Understanding Reported Scores
When present, an entry can display a stored value from 0 to 100. It is a report payload field, not a calculated risk, fraud estimate, audit result, or safety verdict. Community submissions may have no score. Registry rows do not always include an independently verifiable source marker.
| Stored Field | Registry Label | What It Means |
|---|---|---|
| Value present | Stored Report Value | The value supplied by the reporting path; it does not establish fraud, safety, or loss |
| Value absent | Reported Entry | A report was recorded without a stored score |
3.2 How Scores Are Recorded
The arcade report path sends riskScore: 80 for a destroyed live listing without using a score threshold gate. This fixed stored value is a reporting payload, not the separate age/liquidity gameplay heuristic and not a calculated risk or fraud estimate. A separate React-based game path may submit different report fields. Do not present third-party scanner scores or methodologies as protocol facts.
4. Warning Signs Explained
The registry can record warning-sign labels. A label is supplied by a reporting path or submitter and is not independent verification:
| Warning Sign | Registry Meaning and Limit |
|---|---|
| LOW_LIQUIDITY / NEW_TOKEN | Labels used by the arcade report payload; they are not an on-chain finding or fraud conclusion. |
| GAME_IDENTIFIED | A game-report label, not verification of the token or project. |
| USER_REPORTED | The manual form's default when no warning signs are entered; it is an unverified submission. |
| Other warning-sign text | May be supplied by a separate game path or a community submitter; review the original evidence independently. |
No automated checker guarantees safety. Reported labels, scores, and source descriptions should not be treated as safe/unsafe classifications.
5. Searching the Registry
5.1 Current DexScreener Market-Listing Search
The search bar requests current third-party market-listing information from DexScreener. The registry query uses text/substring matching, not verified token identity; it does not audit a mint address or verify contract behavior:
- Type in the search bar: Enter a coin name, ticker, or contract address (for example,
DOGEorPEPE). - See current market-listing text matches: A dropdown shows DexScreener results. The same name or symbol can represent multiple pairs.
- Select a listing: Click a result to place that listing's name into the registry search. This does not preserve a verified token identity.
- Compare independently: Compare the chain and full pair/address before treating a returned row as relevant. A returned row is a text match, not an identity confirmation.
5.2 Chain Filter
Filter the registry by blockchain:
- Click the chain dropdown (defaults to All Chains).
- Select a specific blockchain.
- Review the reported entries returned for that chain.
5.3 Interpreting Text Matches
Registry results are text matches from the submitted query and selected filters, not verified token-identity matches:
- Review the recorded name, symbol, chain, pair/address, score, concern label, source, date, and warning-sign text.
- The selected DexScreener listing contributes its name as search text; the same name or symbol may appear across different pair addresses.
- Compare the chain and full pair/address independently using DexScreener and explorers.
No text match means no registry row matched the submitted text and current filters. It does not establish token identity, safety, or the absence of a report.
6. Game-Derived Reports from Gameplay
6.1 How the Game Can Feed the Registry
The arcade reporting path can send a destroyed live listing without a score threshold gate to /api/rugpull/game-report. Its payload includes riskScore: 80, along with listing fields and fixed game-report labels. The stored 80 is a reporting payload, not a calculated risk or fraud estimate. The separate age/liquidity gameplay heuristic must not be treated as the stored report value.
6.2 What Gets Saved
| Data Saved | Source and Limitation |
|---|---|
| Token name and symbol | Live listing fields included in the report payload |
| Signal score | Fixed stored report payload value 80; not a fraud probability |
| Blockchain / chain | Listing field included in the report payload |
| Pair address | Listing field included in the report payload |
| Warning-sign labels | Fixed game-report labels; not verified findings |
This arcade payload does not add a source marker. A separate React-based game path may submit different contractDetails and warning-sign fields; the registry does not normalize those paths into a calculated score.
7. Submitting a Token-Risk Report
7.1 Community Reporting Form
Anyone can submit a token-risk observation to the registry:
- Click "Submit a Token-Risk Report" in the registry interface.
- Enter a contract address or ticker: Current DexScreener listings may be suggested.
- Select the blockchain: Choose from the supported chains.
- Describe the warning signs: Explain what you observed, with specific evidence where possible.
- Submit: The submission is recorded under the existing flow; recording does not verify the claim.
7.2 Backend Reporting and Verification
The backend reporting flow grants no XP and does not establish a reporting reward. Submitting a report records an observation only; it does not establish a reward or verify the claim.
7.3 Reporting Guidelines
- Only report observations you can describe factually.
- Include an address, transaction, source, or timestamp where available.
- Do not report tokens out of personal rivalry or for market manipulation.
- Community review or moderation does not turn a submission into a verified finding.
8. Using the Registry for Research
8.1 Before Interacting With Any Token
Recommended research workflow:
These are manual follow-up checks, not analyses performed by the registry or the arcade report payload.
- Search the reported token-risk registry by text, then compare the chain and full pair/address independently.
- Optionally cross-reference independent third-party tools; methods vary and SiCierto does not endorse their scores.
- Verify current token authorities, program details, and pool conditions using official documentation and an independent explorer.
- Review the token's official social channels, documentation, holder distribution, liquidity positions, and lock or vesting evidence.
- Review off-chain warnings such as impersonation, urgency, pressure tactics, or guaranteed-return claims.
For protocol definitions, consult Solana token documentation, Set Authority, Token Extensions, and Raydium documentation. For off-chain investment-fraud warnings, consult the FTC investment-scam guidance and Investor.gov crypto-asset guidance.
8.2 Warning Signs to Watch Independently
Beyond the registry, watch for:
- Anonymous or impersonated teams with no independently verifiable background
- Unrealistic promises such as "1000x guaranteed"
- Copycat names, addresses, or social accounts
- Pressure to buy immediately before a claimed price event
- Liquidity arrangements that are unclear, removable, or locked only briefly
These are warning signs to investigate, not proof of fraud by themselves.
9. Frequently Asked Questions
Q: What does it mean when no text match is returned?
A: No registry row matched the submitted text and selected filters. Text matching does not establish token identity, safety, or the absence of a report; compare the chain and full pair/address independently.
Q: How quickly are game-derived entries added?
A: The arcade path can submit a record when its existing report flow runs; other game/report paths may differ. Submission timing does not make a report verified.
Q: Can I remove a false positive from the registry?
A: Contact support through the platform with evidence that the entry needs correction. Review of a request does not endorse either claim.
Q: Does the registry cover all blockchains?
A: No. The interface currently supports 14 chains, and coverage is not exhaustive within them.
Q: Does submitting a report earn XP or a reward?
A: No. Backend reporting grants no XP or reporting reward. A submission records an observation only and does not establish a reward or verify the report.
Q: What's the difference between the registry and the Rug Pull Hunter game?
A: The game is an educational arcade experience that can produce simplified game-derived records. The registry is a persistent searchable collection of community submissions and game-derived reports. Neither is a contract auditor or safety oracle.
10. Tips for Effective Use
| Tip | Why It Matters |
|---|---|
| Search before you interact | A registry search can provide a starting point for independent research |
| Check current authorities | Mint, freeze, metadata, and other permissions need direct verification |
| Read the report source and date | Community submissions and game-derived reports have different provenance and can become stale |
| Cross-reference multiple sources | No registry, scanner, or market listing guarantees safety |
| Watch liquidity terms | Lock dates, pool mechanics, and withdrawal permissions need independent review |
11. Disclaimer
The Reported Token-Risk Registry is an educational and research tool. Entries represent reported observations or game-derived signals, not legal findings, verified fraud determinations, or financial advice. DexScreener information is third-party market-listing data. No text match, score, label, or absence of a text match proves safety. Conduct independent research before making investment decisions. SiCierto is not responsible for losses resulting from tokens listed or not listed.
Copyright 2026 SiCierto. All rights reserved.