| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| Sellable | No — transfers blocked | ChainSift simulation | 14 Nov 2026 |
| Buy tax | 0% | Contract | 14 Nov 2026 |
| Sell tax | No data | Contract | 14 Nov 2026 |
| Admin mint | No data | Contract | 14 Nov 2026 |
| Transfers pausable | No data | Contract | 14 Nov 2026 |
| Address blacklist | No data | Contract | 14 Nov 2026 |
| Upgradeable proxy | No data | Contract | 14 Nov 2026 |
| Source verified | No | Block explorer | 14 Nov 2026 |
| Top-10 holders | 75% | Holder distribution | 14 Nov 2026 |
| Liquidity locked | No | LP holders | 14 Nov 2026 |
| Holders | 735 | Token contract | 14 Nov 2026 |
| Deployed by | 0x7f9822…8a179c |
| Holders | 735 |
| Rank | Address | Share |
|---|---|---|
| #1 | 0x7f9822…8a179c | 74.99% |
| #2 | 0xc4c691…97cd69 | 0.00% |
| #3 | 0x095261…198b86 | 0.00% |
| #4 | 0x020921…7f813b | 0.00% |
| #5 | 0x911a2a…de0b05 | 0.00% |
This automated check simulated a sale of ONS on BSC and found that selling is blocked by the contract — this is what's known as honeypot behaviour. In practice, this means the contract's code prevents holders from converting their tokens back into other assets once bought, regardless of price, timing, or market conditions. Because this was detected, the check also flagged that the contract source code is not verified, meaning the publicly available bytecode hasn't been matched to readable source code, so the exact logic behind the sell restriction (and anything else the contract might do) can't be independently confirmed from outside. The check additionally found that the top 10 wallet addresses hold 75% of the total supply, which means a small number of holders — potentially including the contract owner or associated wallets — control the large majority of tokens, and that liquidity is not locked, meaning whoever controls the liquidity pool could withdraw it at any time without a time-lock contract preventing them from doing so. Several other mechanics, including sell tax, admin mint ability, transfer pausing, address blacklisting, and upgradeability, returned no data and were not assessable from the available contract state on the date of this check.
It's worth being clear about what this check does not cover. This is an automated read of contract mechanics only — it does not assess who is behind the project, their intentions, the token's economic design, marketing claims, roadmap, or any legal structure. A contract can show no detected red flags and still involve undisclosed risk in those areas, and conversely, flagged mechanics don't by themselves tell you anything about who deployed the contract or why. No person has reviewed this token; the result reflects automated simulation and on-chain data as it stood at the time of the check.
Given that selling has been detected as blocked, there is no amount of purchase, however small, that would allow you to test this safely — funds placed into a token that cannot be sold remain in that token. Rather than testing with money, you may want to look at the contract's bytecode or wait for source verification if that becomes available, review the project's own public communications and team disclosures independently, check whether the liquidity pool address shows any lock transaction on the block explorer, and look at how the top holder wallets are labelled or linked on-chain. None of this guarantees an outcome one way or another, but it gives you more to go on than this check alone can provide.
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.