LILPEPE On-Chain Risk Check

Little Pepe · Base · 0x63bbe9ef46d1abc11b5a7ac8c5049e6fd29e740c
0 / 10 On-chain Check
Checked 15 Nov 2026. On-chain Check, 10 of the 100-point ChainSift Score — what it covers. Contract function analysis was unavailable for this contract, so that signal is excluded from the total.

Evidence

Risk factorFindingEvidenceDate
Sellable Yes ChainSift simulation 15 Nov 2026
Buy tax 0% Contract 15 Nov 2026
Sell tax 0% Contract 15 Nov 2026
Admin mint No data Contract 15 Nov 2026
Transfers pausable No data Contract 15 Nov 2026
Address blacklist No data Contract 15 Nov 2026
Upgradeable proxy No data Contract 15 Nov 2026
Source verified No Block explorer 15 Nov 2026
Top-10 holders 96.6% Holder distribution 15 Nov 2026
Liquidity locked No LP holders 15 Nov 2026
Holders 244 Token contract 15 Nov 2026

This contract — LILPEPE

Deployed by0xfd8411…1c81b5
Holders244

Largest holders

RankAddressShare
#1 0xfd8411…1c81b5 95.53%
#2 0x75d409…97315d 0.85%
#3 · contract 0x2a9ec0…9544d6 0.06%
#4 · UniswapV2 · contract 0x7220f9…250602 0.05%
#5 0xc16f0f…8c85e5 0.05%

What this means

This automated check scored LILPEPE 0 out of 10 on Base, and it's worth understanding exactly what that figure is built from. A simulated transaction found the token could be bought and sold with no buy or sell tax detected on the date of the check, so no honeypot behaviour was identified in that test. However, several contract functions — including whether the owner can mint new tokens, pause transfers, blacklist addresses, or upgrade the contract logic entirely — were not reported by the data source and so could not be scored either way. This is not the same as those permissions being absent; it means this check could not confirm their status. Separately, the contract's source code is not verified on the block explorer, so its behaviour is only visible as compiled bytecode rather than readable code, which limits how much any automated or manual review can confirm about what the contract actually does. On top of this, the top 10 holders control 96.6% of the supply, a concentration level that means a small number of wallets could sell in a way that affects the price for everyone else, and the liquidity behind the token is not locked, meaning whoever controls it could withdraw it from the trading pool at any time.

It's important to be clear about what this check does not cover. It reads contract mechanics and on-chain data only — it does not assess who the team behind the token is, whether their stated intentions match their actions, how the tokenomics are designed to play out over time, or whether any legal or regulatory structure sits behind the project. A low or high score here is not a verdict on the people running the project or on their future conduct; it reflects only what could be verified in the contract and holder data at the time of the scan.

Given the unverified source code and the unscored owner permissions, a practical next step would be to look for the contract's source code directly on the block explorer yourself, or to wait until it is verified, since unverified bytecode leaves real gaps in what can be confirmed. It's also worth researching the holder distribution independently, looking into who holds the top wallets and whether any are known exchange or team addresses, and checking the liquidity pool directly to see who controls it and under what terms. None of this check's findings should be read as a recommendation either way; they are inputs for your own further research, not a substitute for it.

Team, tokenomics and legal structure are not assessed here — that is the other 90 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 10 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 15 Nov 2026. A check describes a contract on the date shown; contracts can be changed afterwards.