cryptolicit

Token risk checks on BNB Chain

309 tokens checked on BNB Chain, of which 8 have a property that blocks a buyer. Here the checks read the contract itself: whether selling can be blocked, whether the tax can be changed after you buy, whether ownership was really given up.

Flagged on BNB Chain

Recently checked on BNB Chain

All BNB Chain tokens in the table view →

What can go wrong with a token on BNB Chain

Here a token is a contract somebody wrote, so the risk is in the code. The most direct version is a honeypot: buying works, selling does not. Softer versions do the same job — a tax the owner can raise after you buy, a blacklist that quietly excludes your wallet, a pause switch that stops all transfers at the moment you would want to use them.

Because these powers usually belong to an owner address, the first thing worth knowing is whether ownership was renounced — and whether that renouncement is real, or undone by a hidden owner or a function that takes ownership back. A genuinely renounced contract cannot use owner-only powers at all, which removes a whole class of risk in one step.

The checks read the deployed contract directly, so an unverified contract is itself a finding: nobody, including us, can read what it does beyond its behaviour. On top of that sits the market question — whether the pool backing the token is real money or a number with no trading behind it.

Every finding on this page comes from automated checks of public data, described on the methodology page. They are not an audit and not an accusation against anyone. All 44 checks are explained one by one.