KITE On-Chain Risk Check

Kite AI · Base · 0xb2c6d50eb8a88a9d81c4a55c340d8f886c966bf6
0 / 18 On-chain Check
Checked 20 Nov 2026. On-chain Check, 18 of the 100-point ChainSift Score — what it covers. This token can’t be sold, so the check is 0, whatever the other signals show.

Evidence

Risk factorFindingEvidenceDate
Sellable No — transfers blocked ChainSift simulation 20 Nov 2026
Buy tax 0% Contract 20 Nov 2026
Sell tax No data Contract 20 Nov 2026
Admin mint No data Contract 20 Nov 2026
Transfers pausable No data Contract 20 Nov 2026
Address blacklist No data Contract 20 Nov 2026
Upgradeable proxy No data Contract 20 Nov 2026
Source verified No Block explorer 20 Nov 2026
Top-10 holders 89.8% Holder distribution 20 Nov 2026
Liquidity locked No LP holders 20 Nov 2026
Holders 1774 Token contract 20 Nov 2026

This contract — KITE

Deployed by0x044c9a…6496ec
Holders1,774

Largest holders

RankAddressShare
#1 0xfd92f4…2a7eda 13.66%
#2 0xbaed38…e9439f 13.32%
#3 0x3304e2…7b566a 13.09%
#4 0x0d0707…b492fe 12.92%
#5 0x1985ea…b25c87 12.70%

What this means

This automated check on KITE (Kite AI, Base chain) returned a score of 0 out of 18, and the evidence behind that score points to a serious problem rather than a minor one. The simulation detected honeypot behaviour: selling was blocked by the contract at the time of the check. In practice, this means wallets that hold this token may not be able to convert it back out, regardless of how the price appears to move. A buy tax of 0% was recorded, but sell tax data was unavailable, which is consistent with a contract that is structured to let tokens in but not out. On top of this, the top 10 holders control 89.8% of the supply, concentration at this level means a small number of wallets could move or dump a large share of supply, affecting the market for anyone else holding the token. The contract source code is not verified, so the actual logic behind these behaviours sits in bytecode only and has not been independently readable on the block explorer. Liquidity is not locked, meaning whoever supplied the trading pool is free to withdraw it at any point, which can leave a token without a functioning market even if selling were otherwise possible.

It's important to be clear about what this check does not cover. This is an automated read of contract mechanics only, it does not assess who the team behind KITE is, how the tokenomics are designed to play out over time, whether any legal structure or registration exists, or what the intentions of the deployer are. A clean mechanical read does not speak to any of that, and conversely, flags like these do not tell you anything about motive, only about what the contract currently permits the owner or deployer to do.

Given that selling is blocked, this is not a situation where putting in a small test amount makes sense, any funds placed into a token that cannot be sold remain in the wallet by design, there is no transaction size that resolves that. Beyond this report, next steps that sit outside automated contract checks include looking at whether the project or team has any public, verifiable track record, checking community channels for other holders reporting the same selling restriction, and reviewing the contract on the block explorer once (or if) it becomes verified. None of this replaces independent judgement, and nothing in this report should be read as a recommendation to buy, sell, or hold.

Team, tokenomics and legal structure are not assessed here — that is the other 82 points of the ChainSift Score. How this check works and what it misses.

Watch this contract

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 send one confirmation message and nothing else until something changes.

We checked 18 points out of 100.

A deep check also reviews the project's public materials, team, tokenomics and disclosures.

Related guides

Contract data read from GoPlus Security and the Base block explorer. The trade simulation (a buy, then a sale an hour later) is run by ChainSift directly on Base — our data source returned none for this contract. Scores are calculated by fixed rules from that data — no language model decides them. Last updated 20 Nov 2026. A check describes a contract on the date shown; contracts can be changed afterwards.