How to read Monad token risk signals.
Halven Intelligence is built around a simple idea: separate verified facts, creator or user disclosures, and modeled risk so communities do not treat every claim as equal proof.
Verified facts, submitted disclosures and modeled risk are not the same thing.
Halven separates what is read from chain, what a creator or user submits, what a creator signs, and what a calculator estimates. That separation helps communities avoid turning weak claims into false certainty.
Independently read onchain fact
Token supply, balances, market state, pool matches and contract values read directly from Monad.
Contract source status
Whether source code is published and matched on MonadScan or another source, not whether the token is safe.
Submitted disclosure
A market link, custody claim, wallet label, planning note or evidence link supplied by a user.
Creator-signed disclosure
A disclosure signed by an identified creator wallet. It proves who signed the statement, not that future behavior is safe.
Decompiled-bytecode read
A best-effort live read from an unverified contract using decompiled selectors, currently used for Fuze market state where source is not verified.
Modeled estimate
Price impact, expected-sale movement, holder exit risk or incentive stress calculated from assumptions.
Read each Token Facts page in layers.
1. Contract facts
Start with name, symbol, decimals, supply, dead-address balance and whether Halven recognizes the token template.
2. Permission classification
Halven template tokens can be classified more strongly. Generic ERC20 permissions remain unclassified until reviewed.
3. Market Transparency
Check Uniswap, PancakeSwap, Fuze Terminal, Nad.fun or other venue profiles. Live market state does not prove safe or locked liquidity.
4. Wallet disclosure
Look for submitted or creator-signed labels and compare balances against total supply.
5. Distribution intelligence
Use live holder rankings if available, or manual holder modeling when the holder indexer is unavailable.
6. Readiness and report
Use the scorecard and public report as a summary of unresolved transparency questions.
Market depth is venue-specific
A token can trade through AMM pools, bonding curves, launch terminals or several venues at once. Halven separates supported live reads from submitted venue disclosures so users can see what is actually known.
Holder exit risk needs context
Concentration becomes dangerous when a large wallet can sell an amount that overwhelms available market depth. Disclosed treasury, pool and bonding contracts should be separated from ordinary undisclosed-holder risk.
Bonding curves are not AMM pools
For Fuze-style markets, MON raise progress and token allocation sold can differ. A curve may sell a large share of bonding tokens before it reaches the same percentage of its MON target.
Reports are transparency trails
A public Token Facts report combines onchain facts, submitted or signed disclosures, decompiled-bytecode reads and modeled assumptions. It is not an audit, rating or guarantee.