On-chain security analysis — is it a scam or legit?
BNB ChainThe KOTAI contract is a standard ERC-20 token implementation with additional administrative functionality for burning unsold tokens via a designated claim contract.
Read the full analysisEach factor is an on-chain fact recorded at the time of this analysis. The score is computed from them by a deterministic function, so the same contract returns the same score for anyone who runs the audit. How scores are computed
Share held by contracts — treasury, vesting, bridge or staking — is discounted against share held by wallets when the score is computed: a contract cannot decide to sell the way an anonymous holder can, though it can still be drained or voted to sell. Effective concentration is the figure the risk score is actually calculated from.
Holder balances as recorded by the audit of Oct 29, 2026
The risk score reads depth across every pair.
The LP tokens of the analysed pool are not locked or burned, so whoever holds them can withdraw that liquidity.
0xe009…94210x234b…758b0x3e44…b36cNo privileged address appears among these holders: the unlocked liquidity sits with independent providers, not with the deployer.
The ten largest holders own 100.0% of supply. What remains: 99.9% in wallets, 0.0% in other contracts. The deployer/owner wallet itself holds 95.0%. A holder that also controls the contract can sell into its own liquidity. 1,222 holders in total.
Watch the largest wallets that are not exchanges, pools or locks — those are the ones that can move the price.
Acknowledged
0.0% of the pool's LP is burned or time-locked. 100.0% is held, unlocked, by 2 address(es) other than the owner/deployer. One of them — a wallet, 0xe009…9421 — holds 97.0% and can remove that share at once; who controls it is not visible on-chain, so it is not treated as an independent provider. Some pools are concentrated-liquidity (V3/V4) positions; shares above are by position as GoPlus reports them.
Check the lock's end date and beneficiary on the locker's own page before relying on it.
Acknowledged
The verified source code was reviewed and no issue rising to Informational severity or above was identified. This is a statement about the code that was read, not a guarantee: the review covers the published source only. Fact-layer checks (mint/owner authority, mint capability, holder concentration) were applied separately and feed the risk score.
Re-check after any contract upgrade or ownership change, both of which can alter behaviour without changing this page.
Acknowledged
Listed on CoinGecko as KOTAI (KTI). 1,222 holders.
Match the contract address against the project's official channels before trading.
Acknowledged
Liquidity $1.7M (GeckoTerminal, all pools). 24h trading volume $76K (CoinGecko, all markets, daily snapshot). 24h trading volume $33K (GeckoTerminal, all pools).
Size any position to the liquidity and daily volume shown — they set how much you can sell and at what price.
Acknowledged
A token issued by a project for use, governance or fundraising. Scored on its contract and market facts. The class itself adds no points; the contract and market facts decide the score. Basis: no class-specific evidence. Tokenomics — Supply: fixed — the contract has no mint function. Control: a single wallet (EOA). Code: not upgradeable (no proxy). Fees: no buy or sell tax. Market: $1.7M of DEX liquidity across 13 pools. Launch: 15 days of market history.
Check the project's own documentation for what the token is used for; this report covers what the contract allows.
Acknowledged
The token's oldest DEX pool is 15 days old. Age is not part of the risk score — a new token is not a risky one by default — but a short history means fewer trades and holder changes behind the facts in this report.
Re-check ownership, liquidity and holder distribution as the token matures; those are the facts that move early.
Acknowledged
The KOTAI contract is a standard ERC-20 token implementation with additional administrative functionality for burning unsold tokens via a designated claim contract. The codebase is clean, follows standard OpenZeppelin patterns, and contains no complex logic that would introduce significant attack vectors. No vulnerabilities were identified during the static analysis of the provided source code.
The architecture utilizes standard ERC-20 compliance, ensuring compatibility with existing DeFi ecosystems. 7.1 Architecture is robust, relying on established libraries for token transfers and ownership management. 7.2 Code Security is high, as the logic is minimal and avoids complex state dependencies. 7.3 Access Control is correctly implemented using the Ownable pattern for administrative tasks.
7.4 Economic and 7.5 Governance aspects are centralized under the contract owner. The owner has the authority to set the claim contract, which is the only entity permitted to trigger the burnUnsold function. This centralization is typical for token distribution phases but requires trust in the owner's address.
7.7 Upgrades are not supported as the contract is not a proxy. The implementation is immutable, which provides security against logic-swap attacks but prevents future feature updates. 7.8 Operations are straightforward, with clear administrative boundaries.
The contract is secure and ready for deployment. We recommend that the owner address be transitioned to a multi-signature wallet or a DAO-controlled contract to mitigate the risks associated with a single point of failure for administrative functions.
Ensure that the address designated as the 'claimContract' is thoroughly audited before deployment, as it holds the exclusive privilege to burn tokens from its own balance. No further technical changes are required at this time.
Free for any token on the record. It links to this page and always shows the current score and the date it was checked.
Score changes are recorded as dated snapshots — history is append-only and cannot be edited.
Our AI-powered scanner gives you a deeper, real-time smart contract analysis — free, with every scoring factor shown.
Get Detailed Audit Is this your token? Add your links and get it Verified
