Dev wallet: 3ntEpydDjraXrnwWTCJM7DvfBvtYUMc7q1oHADMCoFuK
Project Checker
Run a token diagnostic from mint input. MYTOKEN checks indexed data first, then falls back to provider scans with safe indexing rules.
Project Checker
Enter a token mint/address to run a structured diagnostic. MYTOKEN checks indexed data first, then scans trust and wallet signals when needed.
Archive rows
5
Repeat-offender rows
5
Wallet-linked rows
5
How checker and archive work
Checker lookups are DB-first. On misses, MYTOKEN can run a fresh scan and index only if retention rules are met. The archive below remains the supporting rugged/history discovery layer.
Rugged Archive
Open rugged-only directoryDev wallet: BAGSB9TpGrZxQbEsrEznv5jXXdwyP6AXerN8aVRiAmcv
Dev wallet: 4PGHANfRp8ktHvTEWUuKSimHwG3BR5E34QEFSq3Ec8Hb
Dev wallet: DqeVuNmymZEqzNQmFUvMGAL6xaB49TN7yCmx3h3FpYaK
Dev wallet: HgX4kS1Svt7DZ4VqZz14j6Uk8TCLjFRXFD5Stcucxx3K
How the Project Checker and Rugged Archive Work
The MYTOKEN Project Checker runs a diagnostic lookup for any Solana token mint address or project identifier. When you submit a mint, MYTOKEN first checks its indexed database for an existing profile. If a match is found, the checker returns the full indexed context immediately — including health status, wallet intelligence, market snapshots, and any rugged or stalled signals. If no indexed record exists and the mint passes the retention rules, MYTOKEN can trigger a fresh provider scan and index the token into the research database.
What the Rugged Archive Shows
The Rugged Archive above is a curated view of tokens that MYTOKEN has evaluated and classified as rugged based on a combination of signals: a severe market cap decline from peak, very low remaining liquidity, developer wallet history, rugcheck provider risk scores, and on-chain holder concentration data. Each entry in the archive includes the developer wallet when resolvable, so you can cross-reference whether the same wallet has launched multiple tokens with rugged outcomes.
Understanding Repeat Offender Wallets
A key feature of the MYTOKEN rugged archive is wallet-level grouping. When a developer wallet is linked to two or more tokens that have received a rugged classification, those entries are labeled as repeat offender rows. This cross-token wallet tracking is part of MYTOKEN's independent intelligence layer — it is not based on owner-submitted information and cannot be removed by a verified claim. The purpose is to give researchers a broader signal about launch behavior patterns, not just individual token outcomes.
Limitations of This Data
The rugged classification is an automated heuristic based on indexed market data, and is not a legal determination of fraud or wrongdoing. Developer wallet attribution is based on on-chain authority and signer data, and may not always identify the actual human operator. Always conduct independent research before drawing conclusions about a specific project or wallet. See the methodology page for a full explanation of how classifications are made.