Bitcoin on-chain analysis, market cycles, and holder behaviour at The Markets Unplugged. Creator of Alt Sector Radar. Covers how on-chain signals map to cycle phases.
This guide is a verification workflow you can run before buying any token. It is built to catch the most common ways crypto buyers lose money: hidden contract powers, thin liquidity, blocked exits, and projects that look strong from a chart but cannot survive scrutiny.
For quick definitions of contract powers, liquidity, DEX, and approvals, the Crypto Glossary covers the technical terms used here. For the deeper rug pull and honeypot framework, the rug pulls and honeypots guide pairs naturally with this one.
This is a repeatable workflow for verifying any token before buying. It prioritises exit ability, contract power checks, and liquidity ownership first, then moves outward into fundamentals and narrative. The single most important principle is this: a token can look perfect on a chart and still be untradeable, or controlled by an owner who can change taxes, pause trading, or blacklist your wallet. Until you have confirmed you can actually sell, you have no position you can manage. The goal of this workflow is to catch hidden admin powers, thin liquidity traps, and promotion-heavy deals that fail basic scrutiny before any real capital is committed.
Key points
Most crypto losses come from avoidable mistakes: weak contract control, thin liquidity, and not testing exits before sizing up.
Start with primary sources, then verify contract powers, holder concentration, liquidity ownership, and unlock schedules.
Treat "can I sell" as a required check. A tiny buy and tiny sell on a fresh wallet, before scaling, catches honeypots that pass every other test.
Build a simple evidence trail (links, screenshots, transaction hashes) so you can review decisions later. Memory is unreliable.
Position size after the workflow passes: tiny first, scale only after the position survives two clean weeks. Sizing is part of the safety system.
No checklist catches everything. Off-chain agreements, hidden control, and regulatory action sit outside what on-chain verification can see.
The Principle Underneath The Workflow
Most crypto losses are not bad luck. They are predictable outcomes of skipped checks. A few minutes of structured verification catches the majority of disasters before any real capital is committed: contract control, liquidity and holder concentration, unlock schedules, and whether sells actually work.
The principle that makes the workflow effective is straightforward. Exit ability comes before upside. A token that cannot be sold, or that can be made unsellable by the owner, has no upside that matters. Until exit is confirmed, no other analysis is worth doing.
The reframe: Most beginner research starts with thesis (why this might go up) and ends with risk checks added on at the end. Reverse that. Start with risk checks. If the risk checks fail, the thesis does not matter. If they pass, then the thesis is worth evaluating.
The 5-Minute Quick Check
If you have five minutes and are tempted to buy something on a recommendation, run these six steps before doing anything else.
1
Verify the token address from official docs
Find the contract address on the project's main website or verified docs. Never copy it from a Telegram message, a reply, or a tweet you did not seek out yourself.
2
Check verified code, proxy status, and admin powers
On the block explorer, confirm the contract is verified. Note whether it is a proxy (upgradeable), and what powers the owner has retained.
3
Scan holders and liquidity ownership
Look for extreme holder concentration. Check whether the liquidity pool tokens (LP) are locked, or held by an insider wallet that can pull liquidity at will.
4
Look for changeable taxes, blacklists, pauses, and upgrade hooks
Scan the contract for functions like setTax, pause, blacklist, and upgrade. These are the levers that can be used to change the rules after you buy.
5
Tiny buy, tiny sell, on a fresh wallet
Confirm selling actually works before sizing up. A fresh wallet with no other holdings tests the path end to end. If sells fail or revert, walk away.
6
Log links, screenshots, and the top three risks
Write down the contract address, the explorer link, the LP lock proof, and the three most likely ways this could lose you money. Future you will thank present you.
Pre-Setup Hygiene
Before researching any individual token, set up your wallet and tooling so that the research itself does not put you at risk.
Foundation hygiene
Self-custody first: Hardware wallet for long-term holdings. Small hot wallet for testing and unfamiliar contracts. Never connect the cold storage wallet to research-stage activity. Self-custody basics covers the principle.
Read-only tools only: Block explorers, holder trackers, allowance managers. Anything that requires write access to your wallet should be approached as a separate signing decision, not a research tool.
API discipline: If you use exchange APIs for portfolio tracking, use read-only keys only. Rotate them quarterly. A leaked write-permission API key is a fast path to losses.
OpSec basics: Unique email per venue, app-based 2FA on every venue, password manager. The boring layer that prevents most account takeovers.
The 12-Step Verification Workflow
Use this as a process reminder. Order matters: control checks first, story second. Most disasters fail in steps 5, 6, and 7. By the time you reach steps 8 to 12, you should already know whether the token deserves a deeper look.
1
State the thesis
One line on why this exists: the problem, the users, what success looks like. If you cannot state it cleanly, you do not understand the project well enough to buy yet.
2
Primary sources only
Project website, docs, whitepaper, GitHub or audits, founder posts on verified accounts. Avoid Telegram rumour loops, "alpha groups", and reply-guy summaries. The further you are from the primary source, the more likely the information is wrong.
3
Team and track record
Named people with prior projects and delivery history, or a true community-run protocol with clear governance. Anonymous teams can still build, but the bar of evidence required is higher because there is no track record to anchor against.
4
Token and economics
Total supply, emissions schedule, upcoming unlocks, whether the token has utility or is pure value extraction. Draw the unlock timeline and note who receives what at which date. Unlocks are scheduled supply, and supply matters more than narrative when prices reset.
5
Contract surface
On the block explorer, check for verified code and proxy status. Search the source for sensitive functions: mint, pause, upgrade, setTax, blacklist, setFee. Each one is a lever the owner can pull. Admin keys covers what these functions actually allow in practice.
6
Holders and liquidity
Top wallets and concentration levels. LP ownership and lock duration. Concentration above 30 to 40 percent in non-team-tagged wallets, or unlocked LP, are hard passes. Liquidity in crypto covers why this matters.
7
Trading safety
Are taxes fixed at the contract level or changeable by the owner? Is there a trading pause function? Are there fee switches that can be flipped? Then simulate a tiny buy and tiny sell on a fresh wallet. This is where honeypots fail.
8
Roadmap versus shipping
What has actually shipped in the last 90 days? Recent commits, audits, version notes. A roadmap is a wish list. Shipping is evidence.
9
Ecosystem fit
Real integrations, oracle support, bridges, index inclusion, real users. Not just impression counts, social media metrics, or paid mentions. Ask whether the project would still exist if the marketing budget went to zero.
10
Regulatory and geographic notes
Claims that imply securities exposure, region-blocked sites, KYC requirements for usage. Note the jurisdiction of the issuing entity and your own jurisdiction. A token that is fully legal in one country may be restricted or unavailable in another.
11
Risk ledger
List the top three ways you could lose money on this position: contract risk, liquidity risk, counterparty risk, regulatory risk, narrative risk. Then list what would stop you, and at what price or condition you would exit.
12
Position sizing
If everything passes, start tiny. Keep it at 0.25 to 1 percent of portfolio max until the position survives two clean weeks. Only then consider scaling. Sizing is part of the safety system, not a separate decision.
Why this order: Steps 1 to 4 are cheap and fast. Steps 5 to 7 are where most failures get caught. By step 8 you should already be confident the project is structurally sound. If you find yourself reaching step 11 or 12 without having properly cleared steps 5 to 7, restart the workflow.
Weekly analysis live now
A workflow protects you against the worst losses. Cycle awareness is what determines when to size up and when to step back. The weekly member update covers cycle context, KAIROS timing, and the on-chain reads that frame whether the broader environment supports adding risk or reducing it.
Any one of these is enough to skip a project. Multiple flags at once is a stop signal, no further research required.
Contract red flags: Unverified contract code. Owner can mint new tokens at will. Owner can change taxes after launch. Trading can be paused by the owner. Wallets can be blacklisted. Upgrade hooks with no time-lock or multisig governance.
Liquidity red flags: LP unlocked or controlled by a single insider wallet. Liquidity below the level required to support meaningful exits. Single-pool concentration with no secondary venues. LP lock proofs that point to fake or expired locker services.
Token economics red flags: Unlocks with no published schedule, or "vesting" that turns out to be unverifiable. Treasury or team wallet that can dump significant supply at any time. Emissions structure that pays insiders disproportionately.
Project conduct red flags: Promoters using "guaranteed yield" or "risk-free" language. Audits from unknown shops, or audits that turn out to be PDF templates recycled across projects. No real users, just airdrop farming, points-based engagement, or paid promotion. Aggressive private group recruiting that frames participation as urgent.
The On-Chain Checks You Can Run In Minutes
These are the verification steps anyone can run on a public block explorer. None require special tools or paid access. The whole sequence takes around 10 minutes once practised.
Block explorer verification sequence
Read Contract tab: Search for tax-related functions, blacklist functions, upgrade beacons, and pause functions. Note which are present and what they allow.
Write Contract tab: Confirm who can call sensitive methods. Owner-only functions are a power held by a single wallet (or multisig). Public functions can be called by anyone.
Transfers tab: Scan for blocked addresses, suspicious large transfers in or out, or 100 percent tax events that may indicate prior owner activity.
Events tab: Recent mints (new supply created), ownership transfers (control changing hands), upgrade beacon calls (proxy contract logic being swapped).
Holders tab: Exchange-tagged wallets versus uncategorised insiders. Watch for new top wallets appearing just before a price move, which often indicates insider accumulation ahead of news.
The Social Signals That Actually Mean Something
Most crypto social signals are noise: paid mentions, KOL campaigns, manufactured engagement. A few are genuine indicators that real entities are taking the project seriously. Distinguishing them takes practice but the categories are stable.
Independent builders integrating it: Other teams choosing to integrate the project into their own products without being paid for it. This is the strongest signal because integration is expensive and integrators have skin in the game.
Reputable venues listing after due diligence: Listings on exchanges or in indexes that have known due diligence processes carry weight, because those venues are putting their reputation behind the listing. Listings on permissionless DEXs do not.
Open bug bounty with paid findings: A live bug bounty that has actually paid out for findings indicates a project that takes security seriously and has a community of researchers checking the code. A bug bounty with no paid findings can be window dressing.
Transparent treasury and reporting: Public treasury addresses, regular financial reports, clear use-of-funds breakdowns. The bar most legitimate projects clear, and the bar where most weaker projects fail.
Test With Pennies, Every Time
This is the single most useful safety habit in crypto. Before sizing up on any new token, verify the full path works end to end with money you can afford to lose.
1
Use a fresh wallet
A wallet with no other holdings, no token approvals, no history. The point is to isolate the test from anything you care about. Seed phrase hygiene applies as always.
2
Tiny buy
Buy a small amount, the smallest the venue allows that still produces a meaningful test. The aim is to confirm the buy completes, the token shows up, and the wallet records the transaction.
3
Immediate tiny sell
Sell back. Confirm the sell completes, you receive the expected proceeds (after slippage), and no error or revert occurs. This is where honeypots reveal themselves.
4
Cap approvals
When approving the token for the DEX, set a custom spend limit rather than unlimited. Token approvals covers why unlimited approvals are a long-tail risk that survives long after you stop using the protocol.
5
Revoke after testing
If you decide not to size up, revoke the approval. If you do size up, revoke once you exit the position. Stale approvals are a passive risk surface.
Recordkeeping That Saves You Later
Memory is unreliable. The single biggest difference between research that improves over time and research that drifts is whether you keep records of what you actually checked. A simple evidence trail prevents repeat errors and supports honest review when things go wrong.
A minimal evidence trail
Screenshot key pages: Token contract on the explorer, project docs, audit summary page, LP lock proof. These are the artefacts you will want if anything turns out to be misrepresented later.
Save explorer links: Buy transaction, sell transaction, approval transaction, LP lock transaction. Direct links to chain records you can verify at any time.
Log unlock dates: Calendar reminder for major unlock events. Volatility around unlocks is high, and a calendar reminder beats a forgotten unlock.
Export monthly CSVs: Wallet and exchange activity, monthly. Tax reporting later becomes trivial. Reconstruction after the fact becomes possible if records are needed.
What This Workflow Cannot Catch
No checklist catches everything. Honest acknowledgement of the limits is part of using the workflow well. The boundaries are:
Off-chain agreements: Side deals, OTC arrangements, market-making agreements, and undisclosed token allocations sit outside what the chain shows. A project can be structurally clean on-chain and still have a hidden capital structure that affects price discovery.
Hidden control: Multisig wallets, DAOs, and "decentralised governance" can all hide concentrated control behind procedural complexity. The chain shows who signs. It does not show who pays the signers.
Regulatory action: A perfectly clean project can become unavailable in your jurisdiction overnight if regulators classify the token differently. The workflow flags jurisdictional exposure but cannot predict policy moves.
Smart contract exploits: Audits help. Audits do not guarantee. A novel exploit on a previously-audited contract can drain a protocol that passed every check in this workflow.
The workflow is designed to catch the most common ways crypto buyers lose money, which it does. It is not designed to catch every possible loss. Treat it as a strong filter, not a perfect screen.
The One-Page Decision Tree
If everything else in this article gets compressed into a single page, this is it. Run through these questions in order. The first "pass" answer ends the analysis.
1
Can the owner change taxes or pause trading?
If yes: pass. The rules can change after you buy.
2
Is the LP unlocked, or controlled by insiders?
If yes: pass. The exit can be removed.
3
Did the tiny sell test fail?
If yes: pass. The exit does not work.
4
Are audits weak, real users absent, or promotion the dominant signal?
If yes: pass. The fundamentals do not support the price.
5
All checks clean and you still want in?
Start tiny. Size up only after the position survives two clean weeks. Sizing is part of the safety system.
Frequently Asked Questions
No. Audits are helpful but never sufficient. They check the code at a moment in time, against a defined scope, by a specific firm. They do not guarantee the contract is safe. They do not catch governance decisions made after the audit. They do not assess whether the audit firm is reputable. Combine audits with owner-power checks, holder concentration checks, and a tiny exit test.
No. Honeypots and rug pulls trade on DEXs all the time. The fact that a token is only on a decentralised exchange does not make it safer. Contract rules and liquidity ownership decide safety, not the type of venue. A DEX-only token can be more dangerous than a centralised-exchange listing because there is no listing review process between you and the contract.
Expect volatility. Re-run the holder and liquidity checks before adding any size. Recipients of newly unlocked tokens often sell into strength, and the resulting price action can break technical levels that looked clean before the unlock. Calendar reminders for major unlocks are a small habit with significant returns.
It helps, but you still need to label LP joins, staking rewards, bridge events, and airdrops correctly. Trackers automate basic transactions. They struggle with complex DeFi events. Plan for some manual cleanup at tax time, particularly if you have been active across multiple chains. Consult a qualified tax professional in your jurisdiction for material amounts.
For a project you are seriously considering, plan for 30 to 60 minutes of focused research using the 12-step workflow. The 5-minute quick check is for filtering. Anything that passes the 5-minute check and survives the 12-step workflow is worth a tiny test position. The time investment pays back the first time you avoid a project that would have been a loss.
Not always, but the bar of evidence rises. Bitcoin itself was launched by a pseudonymous founder. Some legitimate protocols are run by anonymous teams for security reasons. The question is what other evidence supports the project: real users, audited code, transparent treasury, working product. Anonymous plus weak fundamentals plus aggressive marketing is the dangerous combination.
Owner-controllable taxes and pause functions. A buyer arrives at the chart, sees clean price action, buys, and finds out later that the owner can set tax to 99 percent or pause trading entirely. The workflow catches this at step 5 (contract surface check) before any capital is committed. Liquidity ownership comes second, where unlocked LP held by a single insider can be removed at any time.
A workflow protects you against the worst losses. Cycle awareness is what determines when the broader environment supports adding risk and when it does not. Alpha Insider members get this analysis in real time every week across KAIROS timing, on-chain data, and macro signals.
This guide is for education only, not financial, investment, legal, accounting, or tax advice. Nothing here is a recommendation to buy, sell, or use any product or service. Cryptoassets are high risk and prices can go to zero. Only use amounts you can afford to lose. Availability and legality vary by country, check local rules before acting. You are responsible for your own decisions.
Bitcoin on-chain analysis, market cycles, and holder behaviour at The Markets Unplugged. Creator of Alt Sector Radar. Covers how on-chain signals map to cycle phases.
Technical analysis, macro context, and market structure across Bitcoin, Ethereum, and altcoins at The Markets Unplugged. Creator of KAIROS v6 and the Apex Macro Dashboard.
Technical analysis, macro context, and market structure across Bitcoin, Ethereum, and altcoins at The Markets Unplugged. Creator of KAIROS v6 and the Apex Macro Dashboard.
Technical analysis, macro context, and market structure across Bitcoin, Ethereum, and altcoins at The Markets Unplugged. Creator of KAIROS v6 and the Apex Macro Dashboard.
Technical analysis, macro context, and market structure across Bitcoin, Ethereum, and altcoins at The Markets Unplugged. Creator of KAIROS v6 and the Apex Macro Dashboard.
Technical analysis, macro context, and market structure across Bitcoin, Ethereum, and altcoins at The Markets Unplugged. Creator of KAIROS v6 and the Apex Macro Dashboard.
Technical analysis, macro context, and market structure across Bitcoin, Ethereum, and altcoins at The Markets Unplugged. Creator of KAIROS v6 and the Apex Macro Dashboard.
Technical analysis, macro context, and market structure across Bitcoin, Ethereum, and altcoins at The Markets Unplugged. Creator of KAIROS v6 and the Apex Macro Dashboard.
Technical analysis, macro context, and market structure across Bitcoin, Ethereum, and altcoins at The Markets Unplugged. Creator of KAIROS v6 and the Apex Macro Dashboard.
Technical analysis, macro context, and market structure across Bitcoin, Ethereum, and altcoins at The Markets Unplugged. Creator of KAIROS v6 and the Apex Macro Dashboard.
Technical analysis, macro context, and market structure across Bitcoin, Ethereum, and altcoins at The Markets Unplugged. Creator of KAIROS v6 and the Apex Macro Dashboard.
Technical analysis, macro context, and market structure across Bitcoin, Ethereum, and altcoins at The Markets Unplugged. Creator of KAIROS v6 and the Apex Macro Dashboard.
Technical analysis, macro context, and market structure across Bitcoin, Ethereum, and altcoins at The Markets Unplugged. Creator of KAIROS v6 and the Apex Macro Dashboard.
Technical analysis, macro context, and market structure across Bitcoin, Ethereum, and altcoins at The Markets Unplugged. Creator of KAIROS v6 and the Apex Macro Dashboard.
Technical analysis, macro context, and market structure across Bitcoin, Ethereum, and altcoins at The Markets Unplugged. Creator of KAIROS v6 and the Apex Macro Dashboard.
Technical analysis, macro context, and market structure across Bitcoin, Ethereum, and altcoins at The Markets Unplugged. Creator of KAIROS v6 and the Apex Macro Dashboard.
Technical analysis, macro context, and market structure across Bitcoin, Ethereum, and altcoins at The Markets Unplugged. Creator of KAIROS v6 and the Apex Macro Dashboard.
Technical analysis, macro context, and market structure across Bitcoin, Ethereum, and altcoins at The Markets Unplugged. Creator of KAIROS v6 and the Apex Macro Dashboard.
Technical analysis, macro context, and market structure across Bitcoin, Ethereum, and altcoins at The Markets Unplugged. Creator of KAIROS v6 and the Apex Macro Dashboard.
Technical analysis, macro context, and market structure across Bitcoin, Ethereum, and altcoins at The Markets Unplugged. Creator of KAIROS v6 and the Apex Macro Dashboard.
Technical analysis, macro context, and market structure across Bitcoin, Ethereum, and altcoins at The Markets Unplugged. Creator of KAIROS v6 and the Apex Macro Dashboard.
Discussion