Free above: contract permissions, sell test and tax when data is available.
Paid report: pool balances, trading activity, large holders and estimated price impact for supported pools.
| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| Sellable | Yes | Transfer simulation | 15 Nov 2026 |
| Buy tax | 0% | Contract | 15 Nov 2026 |
| Sell tax | 0% | Contract | 15 Nov 2026 |
| Admin mint | Not present | Contract | 15 Nov 2026 |
| Transfers pausable | Not present | Contract | 15 Nov 2026 |
| Address blacklist | Not present | Contract | 15 Nov 2026 |
| Upgradeable proxy | No | Contract | 15 Nov 2026 |
| Source verified | Yes | Block explorer | 15 Nov 2026 |
| Liquidity locked | 100% burned | LP holders | 15 Nov 2026 |
| Holders | 18 | Token contract | 15 Nov 2026 |
| Deployed by | 0x7451dc…ea9f12 |
| Holders | 18 |
| Rank | Address | Share |
|---|---|---|
| #1 | 0x7451dc…ea9f12 | 100.00% |
| #2 · Uniswap v4 pool · contract | 0x000000…e08a90 | 99.87% |
| #3 · contract | 0xe56f81…4ee756 | 0.26% |
| #4 · contract | 0x410144…0ea4a3 | 0.22% |
| #5 · contract | 0x971b72…a2732c | 0.12% |
This automated check scanned the BITS contract on Ethereum and found no indicators of the mechanics most commonly used to trap or drain holders. A transfer simulation showed the token can be sold, and buy and sell taxes were both found to be 0% at the time of the check. No admin mint function was detected, meaning the contract code reviewed does not contain an obvious path for the owner to create new tokens and dilute holders. No ability to pause transfers was found, so the owner does not appear able to freeze trading at will. No address blacklist function was detected, which would otherwise let an owner block specific wallets from selling. The contract is not an upgradeable proxy, meaning its logic cannot be swapped out later for different behaviour. The source code is verified on the block explorer, so the logic actually running on-chain can be read by anyone, and liquidity is reported as 100% burned, meaning the tokens backing the trading pool have been sent to a dead address rather than held by a wallet that could withdraw them.
What this does not tell you is anything about the people behind BITS, their intentions, or the token's broader economics. A clean contract reading says nothing about whether the circulating supply is concentrated in a few wallets that could sell in size, whether there are off-chain agreements, marketing claims, or a roadmap that will or won't be delivered, or whether the team is anonymous, doxxed, or has a history with other projects. Score and findings here reflect contract mechanics only, as detected on the date of this check; code can also be redeployed, migrated, or replaced by a successor contract at any time, and none of that would show up in this result.
With 410 holders recorded, it's worth looking at how that supply is actually distributed — a small number of large wallets can still present concentration risk even where no contract-level flags exist. Before putting money in, it's worth checking the holder distribution directly on the block explorer, looking at the liquidity pool's trading history and depth rather than just its lock status, searching for the team or project independently of their own marketing, and checking whether the contract or team has any prior history elsewhere. None of this check constitutes investment advice, and nothing here should be read as a guarantee of outcome.
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 12 points out of 100.
A deep check also reviews the project's public materials, team, tokenomics and disclosures.