| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| Sellable | No data | Transfer simulation | 27 Oct 2026 |
| Buy tax | No data | Contract | 27 Oct 2026 |
| Sell tax | No data | Contract | 27 Oct 2026 |
| Admin mint | No data | Contract | 27 Oct 2026 |
| Transfers pausable | Enabled | Contract bytecode | 27 Oct 2026 |
| Address blacklist | No data | Contract | 27 Oct 2026 |
| Upgradeable proxy | No data | Contract | 27 Oct 2026 |
| Source verified | No | Block explorer | 27 Oct 2026 |
| Top-10 holders | 99.9% | Holder distribution | 27 Oct 2026 |
| Liquidity locked | No | LP holders | 27 Oct 2026 |
| Holders | 109 | Token contract | 27 Oct 2026 |
| Deployed by | 0xa4bec3…63aadf |
| Holders | 109 |
| Rank | Address | Share |
|---|---|---|
| #1 | 0xa4bec3…63aadf | 99.62% |
| #2 | 0xd2d8ee…1e3fce | 0.07% |
| #3 | 0x97b55f…93bdff | 0.06% |
| #4 | 0x79430c…2907e4 | 0.02% |
| #5 | 0xd8616e…d4bf65 | 0.02% |
This automated check on Yes (Yes coin), on BNB Smart Chain, returned a score of 0 out of 10, and the findings point to several mechanisms that give significant control to whoever holds the contract's owner permissions. Transfers can be paused by the owner, meaning that at any point, holders could find themselves unable to move or sell their tokens simply because the owner switched that function off. The contract's source code is not verified, which means the automated reading was done on raw bytecode rather than human-readable code, and several contract functions could not be retrieved from the data source at all, so this check could not confirm or rule out other common mechanisms such as admin minting, blacklisting, or buy and sell taxes — those remain unknown rather than absent. Separately, the top 10 holders control 99.9% of the total supply, and the liquidity behind the token is not locked, meaning it could be withdrawn from the trading pool without notice. With only 109 holders recorded, the token's distribution is narrow by most standards.
It's important to be clear about what this check does and does not do. It reads contract mechanics as they existed on the date of the check — things like pausability, ownership permissions, holder concentration, and liquidity lock status. It does not assess the people behind the project, their track record, the token's economic design, any legal or regulatory structure, or their intentions. A contract can show no flags and still involve a team or a plan that creates risk, and conversely, flags like these do not by themselves confirm wrongdoing — they confirm that the technical capability exists.
Given that transfers can currently be paused and liquidity is not locked, it's worth noting that no sellability data was returned for this token, so whether tokens can currently be sold at all was not confirmed either way. Before considering any interaction with this contract, it would be worth seeking out the verified source code directly on the block explorer if it becomes available, checking whether the liquidity pool tokens are held by a known locking contract or by an unlisted wallet, and researching the team or project behind the token through independent channels. Given the unverified source and the unresolved questions around basic functions, treating the available information as incomplete rather than reassuring would be a reasonable starting point.
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 10 points out of 100.
The other 90 are where money is usually lost: who the team is, where the tokens sit, what the documents actually say, and what the project chose not to put on its front page.