Free tools Windows power users keep installed
One-click scans. No signup required.
Evaluate a new token by verifying its identity, reading primary disclosures, checking supply and contract controls, looking for delivered utility, assessing likely liquidity, and identifying the laws and venue rules that apply. An exchange listing is a venue decision—not proof of safety, fair value, adequate liquidity, regulatory approval, or a recommendation to buy. This process helps you find evidence and unanswered questions; it cannot guarantee an outcome or replace token-specific legal, technical, or financial advice.
What should you verify first?
Confirm the exact token and proposed venue
Start a dated record of the full network name, contract address, ticker, token standard, issuer or responsible project entity, official project website, and the specific exchange or trading platform said to be listing the token. A ticker alone is not a unique identifier: unrelated assets can use the same symbol, and scammers can promote a copied or spoofed contract.
- Find the contract address in the project’s primary documentation, then compare it with the address shown on a reputable block explorer for the named network.
- Confirm that the token standard and network match the project documentation; do not assume similarly named tokens on different networks are interchangeable.
- Verify a claimed listing using the venue’s own announcement or listing page. A project’s statement that it has applied, or plans to apply, is not confirmation that the venue will list it.
- Save the date and exact version of each document or announcement you review. The address and details can change, and your assessment should say what information it relied on.
This identity-checking workflow is a practical safeguard, not a universal procedure prescribed by a regulator. If the project will not identify the contract or the venue cannot be independently confirmed, treat those as unresolved questions rather than filling the gaps with social posts.
What do the project’s primary disclosures actually say?
Read the source documents, not just the launch campaign
Read the white paper or equivalent primary disclosure alongside the project’s website, repository, deployed contract, and the venue’s announcement. Compare claims across them. Note contradictions and absent details explicitly; a polished white paper does not prove that its claims are true.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitches#1 Best Overall
For crypto-assets within the MiCA framework that are other than asset-referenced tokens (ARTs) or e-money tokens (EMTs), ESMA’s MiCA disclosure list covers, among other things, the project and people involved; milestones and resources; the offer or intended admission, venue and costs; token characteristics and rights; transfer restrictions and supply-change protocols; technology; any audit outcome; and risks relating to the offer, issuer, token, implementation, and technology. The applicable category, disclosure duties, territorial scope, and exceptions depend on the facts. ESMA says fully decentralised status is assessed case by case.
- Who is responsible for the project, and what are their stated roles?
- What is the token meant to do, and which rights or restrictions attach to holding or transferring it?
- What milestones, resources, and costs are disclosed, and which milestones are already delivered?
- What supply changes or transfer restrictions are possible, and who can trigger them?
- What risks, technical dependencies, and audit results are disclosed?
When a document does not answer a question, record it as unknown. Do not treat promotional wording, a third-party summary, or a claimed audit badge as a substitute for the underlying material.
Who controls supply, token rights, and the contract?
Map the supply and its distribution
Build a supply record from published disclosures and, where possible, on-chain information. Keep the categories separate: a maximum supply is not the same as circulating supply, and an allocation is not necessarily available to trade at launch.
Rank #2
- Ideal for Gifting
- Ideal for a bookworm
- Compact for travelling
| Item to record | What to establish |
|---|---|
| Supply | Stated maximum or total supply, circulating amount at launch, and any issuance or burn mechanism. |
| Allocation | Amounts or proportions assigned to founders, investors, treasury, ecosystem incentives, and public sale. |
| Unlocks and restrictions | Vesting dates, release schedules, transfer limits, lock terms, and who can change or enforce them. |
| Holder rights | What holders can claim, vote on, use, redeem, or transfer—and whether those rights can be modified. |
| Privileged actions | Who can mint, burn, pause, blacklist, upgrade, change fees, or otherwise alter how the token behaves. |
Compare disclosed allocations with relevant wallet balances and transfers when the chain data allows it. Do not assume that one address equals one owner: a wallet may represent multiple beneficial owners, while address labels can be incomplete or wrong. Concentrated holdings, discretionary unlocks, or powerful admin permissions are risk factors that merit investigation; none alone proves misconduct.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Inspect the deployed contract and security evidence
Check whether the deployed source code is verified on the block explorer and whether the address matches the project’s stated contract. Identify upgradeability, owner or admin privileges, minting authority, pause and blacklist functions, fee changes, and transfer restrictions. Also identify relevant dependencies such as bridges, oracles, or custody arrangements; a token’s risks may extend beyond its own contract.
If an audit is cited, establish who conducted it, when, which code commit and deployed version it covered, its scope and exclusions, what findings were reported, and whether fixes were verified. An audit is bounded evidence about the reviewed material, not a guarantee that the live system is safe or that later changes were reviewed.
ESMA’s MiCA disclosure categories include the technology and audit outcome if an audit was conducted. For platforms covered by MiCA Article 76, technical reliability is part of the suitability assessment. A 2025 submission to the SEC Crypto Task Force also recommends disclosure on architecture, security model, vulnerability management, audit status, attack surfaces, public block explorers, and source-code access. That submission is a recommendation, not a binding disclosure rule.
Has the project delivered usable utility?
Separate what exists from what is promised
Match roadmap dates and milestones to releases, working software, public code, documentation, named team responsibilities, disclosed resources, and demonstrable usage. A future feature is not current utility. Ask what the token does that could not be done without holding it, whether that function is available at launch, and how a holder exercises or redeems any stated right.
MiCA disclosure categories address project purpose, team, milestones, allocated resources, and—where relevant—the goods or services available for a utility token. Those categories help identify what to examine; they do not independently verify a project’s claims. A roadmap or exchange listing cannot establish adoption, execution, or future demand.
Rank #4
Will you be able to trade or exit on the stated terms?
Assess market depth, not just the displayed price
Confirm the venue and trading pair, then look for meaningful order-book or pool depth, the concentration of both the token and quote asset, expected slippage for the amount you might trade, scheduled unlocks, and the practical ability to withdraw. A quoted price can look attractive while a shallow market makes a sale move the price sharply. Consider whether disclosed market-maker arrangements or lock terms can be independently checked; the existence of a lock claim does not by itself establish that liquidity is secure or enforceable.
MiCA Article 76 says covered EU trading platforms must assess a crypto-asset’s suitability before admission and consider technical reliability and possible association with illicit or fraudulent activity, including issuer and development-team experience, track record, and reputation. The platforms’ rules may set liquidity thresholds and disclosure conditions. This is a platform obligation, not an endorsement, regulator approval, or investor guarantee.
A 2021 paper by Wang and co-authors, “Trade or Trick? Detecting and Characterizing Scam Tokens on Uniswap Decentralized Exchange,” identified more than 10,000 scam tokens in its Uniswap V2 dataset. The authors attributed at least $16 million in gains to scammers, involving 39,762 potential victims. In that dataset, more than 86% of scam liquidity pools had no more than one day between the scammer’s first liquidity mint and burn events, and 37% of pools’ liquidity was removed within one hour. These are findings from the paper’s historical sample and methods—not current prevalence estimates, a forecast for a particular token, or a measure of centralized-exchange listings. They explain why liquidity control and lock terms deserve scrutiny, but cannot tell you the probability that a new token is fraudulent.
Recommended Free Tools
Best Value
- It can be a gift option
- Comes with secure packaging
- Helpful in various ways
Which legal and jurisdictional rules apply?
Do not infer legal status from a ticker or listing
Identify where the issuer, offer, venue, and intended buyers are located, and how the token functions and is marketed. Under MiCA, requirements and exemptions can vary with the token category, whether there is an offer to the public, and whether admission is sought on an EU platform. ESMA’s Q&A explains that territorial scope matters: an exclusively outside-EU platform situation can produce a different white-paper result, while a decentralised exchange listing may amount to a public offer and full decentralisation is assessed case by case.
For the United States, the SEC Division of Corporation Finance labels its crypto-asset FAQs as staff views and says: “The answers to these frequently asked questions (FAQs) represent the views of the staff of the Division of Corporation Finance. They are not a rule, regulation or statement of the Securities and Exchange Commission.” Do not conclude that a token is—or is not—a security based only on its name, exchange listing, or one feature. The answer depends on the particular facts and applicable law.
How should you compare two tokens without inventing a safety score?
Use the same evidence categories for each token and record the date reviewed. A side-by-side comparison makes gaps visible without pretending that unlike risks can be reduced to one reliable number.
| Comparison area | Evidence to compare |
|---|---|
| Disclosure | Completeness, consistency, and version/date of primary materials. |
| People and delivery | Issuer and team identity, stated responsibilities, and evidence of delivered milestones. |
| Supply and rights | Issuance schedule, insider concentration, unlocks, transfer restrictions, and holder rights. |
| Contract and security | Admin powers, verified code, dependencies, audit scope, and unresolved findings. |
| Utility | Live functionality and evidence of actual use, distinct from planned features. |
| Venue and jurisdiction | Confirmed venue, applicable venue rules, and the locations and legal circumstances involved. |
| Liquidity and exit friction | Depth, concentration, lock and unlock timing, withdrawal conditions, and likely slippage. |
| Open questions | Material legal, technical, market, or disclosure facts that remain unverified. |
What should make you pause?
Pause the evaluation or treat the asset as unverified if key identity or control details cannot be checked. Red flags are prompts to investigate, not proof of fraud by themselves.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →- The contract address, network, issuer, or venue claim is missing, inconsistent, or confirmed only by unofficial posts.
- Supply, insider allocations, unlocks, or minting authority are omitted or conflict across documents.
- Admin powers can materially change holder experience, but the project does not clearly disclose who controls them or why.
- An audit is promoted without enough information to identify its date, version, scope, or findings.
- Roadmap claims are presented as delivered product, or stated utility is not available or exercisable as described.
- Liquidity claims rely on a displayed price or an unverified lock assertion rather than depth and control details.
- The applicable offer, venue, or jurisdictional status is unclear, yet the project makes categorical legal claims.
There is no current, globally representative statistic established here for the share of newly listed tokens that are fraudulent. Historical scam-token samples should not be presented as that percentage.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
