How Threat Protection works
What each of Threat Protection's 18 rules checks, the data it reads from GoPlus, DexScreener and CoinGecko, how the score is formed, and what a flag means.
A flag means one thing: one of RatioNexFlow's own rules found its condition met in the data RatioNexFlow could read at the time shown. A flag is not a finding that anyone has acted dishonestly or intends to, and it says nothing about the people behind a token. It is not a prediction and not advice. RatioNexFlow does not predict, and does not guarantee to detect, any hack, exploit, rug pull, scam or similar event. A token with no flags can still lose value, be hacked or fail. Threat Protection is in beta, and RatioNexFlow is not a regulated crypto-asset service.
Which tokens are checked
RatioNexFlow's rules read token contracts on eight chains: Ethereum, BNB Chain, Polygon, Arbitrum, Optimism, Base, Avalanche and Solana. First, RatioNexFlow works out which contract a symbol in your portfolio stands for. It uses the CoinGecko top-250 snapshot it stores every 5 minutes, its own table of known contracts, CoinGecko's page for a top-250 coin, or a DexScreener search for smaller tokens. It checks only a contract it can confirm; otherwise the token shows "Not checked — contract not confirmed". No coin is exempt from the rules. A coin in the CoinGecko top 250 with no token contract on these chains, such as BTC, which runs on its own blockchain, is checked too: there is no contract, holder list or trading pool there to read, so the contract, holder and pool rules do not apply to it; its market figures are read from CoinGecko, and it shows "No token contract on a chain the rules read (CoinGecko)". Any other token with no contract on these chains shows "Not checked — no contract on a supported chain". A coin counts as major when the CoinGecko top-250 snapshot shows all three: among the 20 largest coins by market value, at least 5 years of price history and at least $100 million traded in 24 hours. A major coin is checked like any other: every rule runs and every rule that finds its condition met is listed, but its score is capped at 24, the top of the low band, and it shows "Major coin — score capped at low (CoinGecko)".
Where the data come from
- GoPlus Security (token security API): whether the contract lets its owner change balances, create new tokens, pause or block transfers, or destroy or upgrade the contract; whether selling is blocked; the trading tax; the holder count and the ten largest holders. Thirteen rules read it.
- DexScreener: the token's trading pools on its chain, their liquidity and 24-hour volume, and when the first pool was created; a market value when CoinGecko has none; and, for smaller tokens, which contract a symbol stands for. Four rules read it, one of them together with CoinGecko.
- CoinGecko: which contract a top-250 coin uses, and the top-250 market snapshot with each coin's 24-hour volume; for a coin whose CoinGecko id is known, its list of markets (the first 100) and each exchange's trust score, read without an API key. When RatioNexFlow reads CoinGecko with an API key, also the token's market value by contract address. Two rules read it.
- A public Solana RPC node: for a Solana token, the program that owns each of the ten largest holder accounts and the first 8 bytes of its data, read on-chain.
- RatioNexFlow's own tables: the contract each symbol stands for, the CoinGecko snapshot refreshed every 5 minutes, a list of known exchange, bridge and burn addresses, a label list of project reserves, treasuries, team vesting wallets, and token lock and multisig programs (each entry with its source and the date it was read), and the stored results, kept for up to 6 hours.
These providers are third parties. Their data can be wrong, incomplete or out of date, and RatioNexFlow does not check them against the blockchain itself. When GoPlus returns no data for a token's contract, the token gets no score and shows "Contract not checked — no data from GoPlus"; the market rules still run. When another provider does not answer, the rules that need its data cannot find their condition met, so a missing flag can also mean missing data. When no provider answers, the token gets no score.
The 18 rules
Transfers out blocked or restricted (GoPlus)
- What the rule checks: Whether GoPlus reports that the token cannot be sold, cannot be sold in full, or cannot be acquired. On Solana: whether GoPlus reports the token as non-transferable, or new token accounts as frozen by default. Severity: critical.
- Data it reads: GoPlus token security: is_honeypot, cannot_sell_all, cannot_buy; on Solana non_transferable and default_account_state.
- What it cannot tell you: Why the contract works this way, or who intended it. RatioNexFlow repeats GoPlus's report and does not test the contract itself.
Owner can change balances (GoPlus)
- What the rule checks: Whether GoPlus reports that the contract owner can change holders' token balances. Severity: critical.
- Data it reads: GoPlus token security: owner_change_balance.
- What it cannot tell you: Whether the owner has ever used this power, or will.
Contract can be destroyed by its owner (GoPlus)
- What the rule checks: Whether GoPlus reports a self-destruct function that the owner can use. On Solana: whether token accounts can be closed by an authority. Severity: critical.
- Data it reads: GoPlus token security: selfdestruct; on Solana closable.
- What it cannot tell you: Whether the function will ever be used.
Owner can create new tokens (GoPlus)
- What the rule checks: Whether GoPlus reports a mint function while the contract still has an owner. Ownership counts as given up only when the owner address is empty, the zero address or the burn address 0x000000000000000000000000000000000000dead. On Solana: whether GoPlus reports a mint authority. Severity: high.
- Data it reads: GoPlus token security: is_mintable and owner_address (creator_address when no owner is given); on Solana mintable and the update authority.
- What it cannot tell you: Whether new tokens will be created, how many, or for what. Some projects create new tokens by design.
Owner controls not visible in the standard view (GoPlus)
- What the rule checks: Whether GoPlus reports owner controls that are not visible in the contract's standard owner view. Severity: high.
- Data it reads: GoPlus token security: hidden_owner.
- What it cannot tell you: What the controls do, or who holds them.
Trading tax in or out (GoPlus)
- What the rule checks: Whether GoPlus reports a tax of 10 % or more on purchases or on sales of the token. Severity: high; critical from 25 %.
- Data it reads: GoPlus token security: buy_tax and sell_tax; on Solana transfer_fee.
- What it cannot tell you: Whether the tax can be changed later, or where the tax goes.
Owner can pause transfers (GoPlus)
- What the rule checks: Whether GoPlus reports that the owner can pause all transfers of the token. On Solana: whether token accounts can be frozen. Severity: medium.
- Data it reads: GoPlus token security: transfer_pausable; on Solana freezable.
- What it cannot tell you: Whether transfers have ever been paused, or will be.
Owner can block addresses (GoPlus)
- What the rule checks: Whether GoPlus reports that the contract can block transfers from listed addresses. On Solana: whether token accounts can be frozen. Severity: medium.
- Data it reads: GoPlus token security: is_blacklisted; on Solana freezable.
- What it cannot tell you: Which addresses are blocked, if any. Some stablecoins can block addresses by design.
Token age (DexScreener)
- What the rule checks: Whether the token's first trading pool on its chain was created less than 7 days ago. Severity: high under 1 day, medium under 3 days, low under 7 days.
- Data it reads: DexScreener: the creation time of each of the token's pools on that chain.
- What it cannot tell you: Anything about the project or the people behind it. Every token is new once.
Liquidity against market value (DexScreener, CoinGecko)
- What the rule checks: Whether the liquidity in all of the token's on-chain pools together is less than 5 % of its market value. A pool paired with a base currency such as SOL, WETH, USDC or USDT counts as twice its side in that currency. Severity: low under 5 %, medium under 2.5 %, high under 1 %; at most low when at least 3 centralised exchanges with a CoinGecko trust score of 8 or more list the coin and at least half of its 24-hour volume is off these pools, and the flag then says so.
- Data it reads: DexScreener: the liquidity of each pool holding at least $1,000. CoinGecko: the market value; when CoinGecko has none, DexScreener's market value, or its fully diluted value; the centralised exchanges that list the coin, with their trust scores; and the coin's total 24-hour volume from the top-250 snapshot.
- What it cannot tell you: How much can be traded at a given price, or what is traded off these pools. Liquidity can be added or removed at any time.
One trading pool found (DexScreener)
- What the rule checks: Whether DexScreener lists exactly one pool holding at least $1,000 of liquidity for the token on its chain. Severity: medium.
- Data it reads: DexScreener: the token's pools on that chain and their liquidity.
- What it cannot tell you: Trading on centralised exchanges, or in pools DexScreener does not list.
24-hour volume against liquidity (DexScreener)
- What the rule checks: Whether the 24-hour trading volume across the token's pools is 5 times the liquidity of all its on-chain pools together (counted as for the liquidity rule above), or more. Severity: medium; high above 20 times.
- Data it reads: DexScreener: 24-hour volume and liquidity of each pool holding at least $1,000.
- What it cannot tell you: Who traded, or why. It does not identify any trader or any conduct, and high volume can have ordinary causes.
Top 10 wallets' share of supply (GoPlus)
- What the rule checks: The share of supply held by the token's ten largest holders, leaving out addresses GoPlus marks as contracts, locked or tagged (such as exchanges, pools and bridges), burn addresses, and addresses on RatioNexFlow's own list of exchange and bridge wallets. The condition is met at 40 % or more. Severity: low from 40 %, medium from 50 %, high from 65 %, critical from 80 %. Where GoPlus labels none of the ten addresses, as on Solana, the holders are read on-chain instead: addresses that are not plain public keys, which only a program can move (pools, locks, multisigs and other programs), are left out, a plain wallet stays counted whatever program its account is assigned to, and the severity is at most medium when nothing identified the holders.
- Data it reads: GoPlus token security: holders (address, share, contract, locked and tag fields) and holder_count. On Solana, a Solana RPC node: the program that owns each of the ten largest holder accounts.
- What it cannot tell you: Who controls these addresses, or whether one person controls several. GoPlus lists only the ten largest holders.
Reserves and program accounts held (GoPlus, Solana RPC)
- What the rule checks: Whether 5 % or more of the supply sits in addresses that RatioNexFlow's label list names as project reserves, treasuries or team vesting wallets, in the accounts of a lock, vesting or multisig program the list names, or, on Solana, in program accounts that no label names. On Solana a holder counts as a program account only when its address is not a plain public key, and a program's label applies only when that program has written its own data to the account. Each label shows its source and the date it was read. These holders are left out of the wallets' share above. Severity: low; medium when program accounts that no label names hold 50 % or more.
- Data it reads: GoPlus token security: the ten largest holders. RatioNexFlow's label list (public.holder_labels: address, kind, source link and date). On Solana, a Solana RPC node: which program owns each holder account, and the first 8 bytes of its data (whether that program has written to it).
- What it cannot tell you: Who controls a labelled address or a program account, whether the supply will be released, or when. For a lock or multisig program's label, RatioNexFlow reads only that the program owns the account and has written data to it, not which kind of account it is. The label list is not complete and is as old as its dates.
Number of holder addresses (GoPlus)
- What the rule checks: Whether GoPlus counts fewer than 200 holder addresses. Severity: medium; high under 50.
- Data it reads: GoPlus token security: holder_count.
- What it cannot tell you: How many people own the token. One person can use many addresses, and an exchange keeps many customers' tokens in one address.
No centralised exchange listing found (CoinGecko)
- What the rule checks: Whether CoinGecko lists no centralised exchange market for the token. RatioNexFlow reads the coin's market list on CoinGecko (its first 100 markets) and counts a market when both sides are named by symbol, not by token address, CoinGecko does not mark it stale or anomalous, and the exchange pays no trading incentive. The rule runs when RatioNexFlow knows the coin's CoinGecko id; no API key is needed. Severity: low.
- Data it reads: CoinGecko: the coin's market list (tickers), by its CoinGecko id.
- What it cannot tell you: Whether a listing exists that CoinGecko does not track.
Contract can be upgraded (GoPlus)
- What the rule checks: Whether GoPlus reports that the token's logic sits behind a proxy and can be changed by an upgrade. Severity: info; it does not change the score.
- Data it reads: GoPlus token security: is_proxy.
- What it cannot tell you: Who can upgrade the contract, or what an upgrade would change.
On GoPlus's trusted list (GoPlus)
- What the rule checks: Whether GoPlus lists the token as trusted. Severity: info; it does not change the score.
- Data it reads: GoPlus token security: trust_list (Solana: trusted_token).
- What it cannot tell you: Anything beyond GoPlus's own list. It is not a check by RatioNexFlow and not a statement that the token is safe.
Major coins and coins on their own blockchain
Major coin — score capped at low (CoinGecko)
- What it means: Whether the coin meets RatioNexFlow's major-coin rule: among the 20 largest coins by market value, at least 5 years of price history and at least $100 million traded in 24 hours. When a figure is missing (the coin is not in the top 250, or the snapshot is more than a day old), the coin does not count as major. A major coin is checked like any other coin: every rule runs, and every rule that finds its condition met is listed with its own severity. Only the score is capped, at 24, the top of the low band; the row says what the rules' own score was. This row is not a rule and is not counted as one.
- Data it reads: CoinGecko's top-250 market snapshot, which RatioNexFlow stores every 5 minutes: the coin's rank by market value, the dates of its all-time high and low (the older one gives its years of price history), and its 24-hour trading volume.
- What it cannot tell you: Anything about the coin beyond the rules' results. Counting as major is not a statement that a coin is safe, and the cap hides no rule that found its condition met.
No token contract on a chain the rules read (CoinGecko)
- What it means: Whether the coin has a token contract on one of the eight chains the rules read. A coin without one, such as BTC, which runs on its own blockchain, has no contract, holder list or trading pool there to read, so the contract, holder and pool rules do not apply to it. Its market figures from CoinGecko are shown, and the major-coin rule is applied to it as to any other coin. This row is not a rule and is not counted as one.
- Data it reads: CoinGecko's top-250 market snapshot, which RatioNexFlow stores every 5 minutes: the coin's rank by market value, its years of price history and its 24-hour trading volume.
- What it cannot tell you: Anything about the coin's own blockchain or its software, or about a contract on a chain the rules do not read: no rule reads them.
When no rule runs
Not checked — no contract on a supported chain
- What it means: Whether the token has a contract on one of the eight chains the rules read.
- Data it reads: The contract RatioNexFlow found for the symbol, if any.
- What it cannot tell you: Anything about tokens on other chains.
Not checked — contract not confirmed
- What it means: Whether RatioNexFlow could confirm which contract the symbol stands for. Many tokens share a symbol.
- Data it reads: CoinGecko, DexScreener and RatioNexFlow's own table of known contracts.
- What it cannot tell you: Anything about the token: no rule was applied.
When the contract data could not be read
Contract not checked — no data from GoPlus
- What it means: Whether GoPlus returned the token's contract data. When it did not (no answer, an error, or no data for this contract), the thirteen rules that read GoPlus, on the contract's permissions, its trading tax and its holders, are not applied, and the token gets no rule score. The market rules still run on what DexScreener returned, and on CoinGecko when RatioNexFlow reads it with an API key. This result is kept for 10 minutes; then GoPlus is asked again.
- Data it reads: GoPlus token security, which returned no data for this contract; DexScreener and CoinGecko (its market value only when read with an API key) for the market rules.
- What it cannot tell you: Anything about the contract or its holders: those rules were not applied. A contract flag that is missing here means missing data, not a contract that was checked.
How the score is formed
Each rule that finds its condition met has a severity: info, low, medium, high or critical. The score starts at the floor of the highest severity (low 10, medium 30, high 55, critical 85). It adds points for each further rule (low 3, medium 7, high 12, critical 18), each further rule counting 60 % of the one before it, up to 100. So one critical rule sets the floor of the score: it is never averaged away. Rule score bands: extreme from 80, high from 55, medium from 25, low below 25. When a critical rule is met, the band is high, or extreme from 90. A major coin is the one exception: its score is capped at 24, the top of the low band, and its band follows the capped score alone. The score sums up rule results. It is not a probability, and not a rating of the token or of the people behind it.
How fresh a result is
A result is kept for up to 6 hours, and the time its data were read is shown with it. Every 15 minutes a background job checks again the results that expire within the hour and that someone asked for in the last 7 days. Opening Threat Protection after a result has expired checks the token again. Re-analyze checks it at once, at most once per token every 10 minutes.
Rule set v9. When the rules change, the number goes up and every stored result is checked again on its next request.
If a flag looks wrong
If a flag looks wrong, use "Report a wrong flag" under the flag in the app. Without an account, write to hello@rationexflow.com. We check every report, and we correct a flag that is wrong.
Couldn't find what you needed? Back to Help Center · email support.