| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| Sellable | Yes | ChainSift simulation | 29 Oct 2026 |
| Buy tax | 0% | ChainSift simulation | 29 Oct 2026 |
| Sell tax | 0% | ChainSift simulation | 29 Oct 2026 |
| Admin mint | Enabled | Contract | 29 Oct 2026 |
| Transfers pausable | Enabled | Contract | 29 Oct 2026 |
| Address blacklist | Enabled | Contract | 29 Oct 2026 |
| Upgradeable proxy | No | Contract | 29 Oct 2026 |
| Source verified | Yes | Block explorer | 29 Oct 2026 |
| Top-10 holders | 100% | Holder distribution | 29 Oct 2026 |
| Liquidity locked | No | LP holders | 29 Oct 2026 |
| Holders | 9 | Token contract | 29 Oct 2026 |
| Deployed by | 0x6f28f4…e1e62f |
| Current owner | 0x6f28f4…e1e62f |
| Holders | 9 |
| Rank | Address | Share |
|---|---|---|
| #1 | 0x6f28f4…e1e62f | 96.19% |
| #2 | 0xbc53f2…39a098 | 3.38% |
| #3 · contract | 0x6e0265…476fa7 | 0.39% |
| #4 | 0xce1b5f…c9dbe3 | 0.03% |
| #5 | 0x188c7c…6a3fb7 | 0.01% |
This automated check scanned Kadana's contract code on BNB Chain and found several functions that give the contract owner significant control over the token after launch. The owner can mint new tokens at will, which means the total supply is not fixed and could be increased, diluting existing holders. Transfers can be paused by the owner, meaning holders could be prevented from moving or selling their tokens at any time, for any reason. The contract also supports blacklisting, so the owner has the technical ability to block specific wallet addresses from transacting. At the time of this check, a simulated buy and sell went through with no honeypot behaviour detected and no buy or sell tax applied, but this reflects conditions on the date tested only — none of these owner-controlled functions require a code change to be activated, so behaviour could differ at any later point. Liquidity is not locked, which means whoever controls the liquidity pool could withdraw it, and top-10 wallets — in this case just 9 holders total — control 100% of supply, indicating extremely high concentration.
It's worth being clear about what this check does not do. It reads contract mechanics only: the functions written into the code and what they technically allow. It says nothing about who the team behind Kadana is, whether they intend to use these functions, what the token's economic model or roadmap looks like, or whether any legal entity stands behind the project. A contract can have owner powers like these and never have them used, or it can look clean on paper while intent elsewhere is poor. This tool cannot assess intent, reputation, or off-chain promises, and no human has reviewed this project — the findings above are generated automatically from the contract and on-chain data.
Before considering any action, it would be worth looking into who holds the owner/admin keys and whether those keys sit behind a multi-signature wallet or timelock, which would at least slow down or add visibility to any use of mint, pause, or blacklist functions. It's also worth checking the liquidity pool directly on a block explorer to see who the LP tokens belong to and whether they could be withdrawn, since liquidity is listed as unlocked here. Given that 9 wallets hold all of the supply, reviewing those addresses' transaction histories may show whether they are linked, newly created, or already moving tokens. Searching for the team's public identity, any audit reports from a named third party, and community discussion of the project elsewhere can also help build a fuller picture than contract mechanics 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.
The other 82 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.