Warnings & Alerts
Warnings and advisories appear after Dexscreener Stats and before Deployer Stats in the full report. The section is headed Alerts & Advisory when a token-lock advisory appears or when saved liquidity-lock data accompanies other warnings or advisories.
Token controls and liquidity
Section titled “Token controls and liquidity”| Warning | What triggered it |
|---|---|
| Dev can mint tokens! / Dev can freeze tokens! | The respective authority remains active. |
| Transfer tax can be changed | An active fee-setting authority without recognized platform attribution. |
| High tax of N% | Current transfer fee is at least 10%. |
| Permanent delegate detected | A delegate can transfer or burn tokens from token accounts. The bot uses stronger slang in this warning. |
| Transfers/mints/burns are currently paused! | Token-2022 pause is active. |
| Token accounts are frozen by default! | New token accounts default to frozen. |
| Potentially sus extension / Unsupported Token-2022 extension | A detected extension needs closer inspection or has no supported decoder. |
| Some Token-2022 extension data could not be decoded | Extension coverage is incomplete. |
| Unlocked LP! | Known lock percentage below 20% for a non-launchpad token. |
| No liquidity! / Low liquidity ($N) | Pool value is zero / below $1,000. |
Locks and liquidity
Section titled “Locks and liquidity”Open View Detailed Report → Locks, or tap View Details in a token-lock advisory. The screen uses evidence saved with the report. If the report has no usable lock evidence, it shows Lock data unavailable for this saved report.
- Scheduled locked shows the known token amount still covered by Streamflow lock schedules. Its percentage uses the token supply. Vault held at last check is the recorded vault balance and can include tokens that have already unlocked.
- Liquidity locks shows the locked share of the selected pool’s LP supply and links to the pool. The LP observation date, unlock schedule, and creator attribution are unavailable in this view.
Launch and wallet activity
Section titled “Launch and wallet activity”| Warning or advisory | What it means |
|---|---|
| Dev sniped / Dev bundled… | Detected early buying. Wording becomes stronger as the supply share grows, up to nearly all the supply. |
| Dev bundled with at least N wallets… | More than two detected bundle wallets; the report may add stronger wording above five. |
| X% was sniped by at least N snipers… | More than 1% detected sniped supply. at launch refers to Pad; after DEX LP mint refers to Dex. |
| Coordinated early buy cluster… | A detected cluster acquired more than 1% of supply. Shows wallet count, percentage, and supported spend. |
| Dev transferred a small / moderate / large amount | More than 0–under 5% / 5–under 10% / 10–under 50% transferred. At 50% or more: Massive airdrop performed by the dev! |
| High / Extremely low top 10 holder % | Top-ten concentration above 30% / below 2%. |
| Dev burned… | A burn was detected; wording scales with the supply burned. |
| Dev manually forced a migration… | A buy exhausted the remaining bonding curve and forced migration. |
| Detected similar funders among early buyers | Investigated buyers share a funding source. |
| Dev has a N% bond rate | Proportion of the creator’s counted launches that bonded. |
| Deployed via known bundling tool | Matching deployment evidence involves a recognized tool. It does not prove every trade was bundled or who controls the wallets; trading-only observations do not trigger this line. |
| Remarks | An additional manually added report note. |
⚠️ and 🚨 flag concerns; neither proves who controls the wallets. Compact reports may omit some alerts. Limited-history reports retain independently observed current control, liquidity, and holder-concentration warnings, but historical activity alerts may be unavailable. Silence is not an all-clear.
