| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| Sellable | No — transfers blocked | ChainSift simulation | 22 Nov 2026 |
| Buy tax | 0% | Contract | 22 Nov 2026 |
| Sell tax | 0% | Contract | 22 Nov 2026 |
| Admin mint | No data | Contract | 22 Nov 2026 |
| Transfers pausable | No data | Contract | 22 Nov 2026 |
| Address blacklist | No data | Contract | 22 Nov 2026 |
| Upgradeable proxy | No data | Contract | 22 Nov 2026 |
| Source verified | No | Block explorer | 22 Nov 2026 |
| Top-10 holders | 17% | Holder distribution | 22 Nov 2026 |
| Liquidity locked | 100% burned | LP holders | 22 Nov 2026 |
| Holders | 6020 | Token contract | 22 Nov 2026 |
| Deployed by | 0x9c33e5…90f408 |
| Holders | 6,020 |
| Rank | Address | Share |
|---|---|---|
| #1 | 0x9c33e5…90f408 | 12.80% |
| #2 | 0xf5e353…f6bbb3 | 0.51% |
| #3 | 0x136ff7…6fa227 | 0.49% |
| #4 | 0x2c85b0…e52dfc | 0.49% |
| #5 | 0x826681…d54e68 | 0.48% |
This automated check simulated a sale of PRIORS on BSC and found that selling is blocked by the contract — this is what's commonly called a honeypot pattern. In practice, this means wallets can buy the token, but the contract's code prevents them from selling it back. Whatever else the check found, this single finding brings the overall score to 0 out of 18, because the ability to exit a position is a precondition for everything else being meaningful. The other findings are still worth noting for context: the contract source code is not verified, meaning no one can read the actual logic behind the bytecode to confirm what it does or why selling fails; the top 10 holders control 17% of supply, which is a moderate concentration rather than an extreme one; and liquidity has been 100% burned, which normally reduces the risk of the liquidity pool being pulled, though it does nothing to address the sell block. Several other checks — admin mint ability, transfer pausing, address blacklisting, upgradeable proxy status — returned no data, meaning the automated scan could not confirm either the presence or absence of these mechanisms from the available bytecode.
It's important to be clear about what this check does not tell you. This is a purely mechanical read of the contract's code and simulated behaviour at a single point in time — the date of this check. It says nothing about who built PRIORS, what their intentions are, how tokens are allocated or vested among the team, whether there's a working product behind it, or whether any claims made about the project elsewhere are accurate. None of that falls within the scope of an automated contract scan, and nothing here should be read as a comment on the people or plans behind the token.
Given that selling is currently blocked, no amount of money put into this token — including a small test amount — would be able to be taken back out under the conditions observed. If you want to understand more before deciding anything, you could look at the contract on a block explorer and see whether the project has published or verified its source code, check whether other wallets besides the top 10 holders have managed to sell recently, and look for any official statement from the team addressing why the sell function appears restricted. Re-running this check at a later date would also show whether conditions have changed, since this result reflects only what was detected today.
Contracts change after they are checked. Tell us where to reach you and we will say when this one does. Free for three contracts, no account.
We checked 18 points out of 100.
A deep check also reviews the project's public materials, team, tokenomics and disclosures.