What is Basecat?

Several unrelated projects share cat-adjacent names, so the only reliable identifier is the contract address above. It is not a vanity address: B20 token addresses are deterministic — [10-byte 0xB2000000000000000000][1-byte variant][9-byte keccak(deployer, salt)] — which is why every real B20 asset starts with 0xb2.

Basecat was created through the o1 launchpad's B20LaunchpadFactory (verified Solidity), whose creation flow called the B20 factory with initialAdmin = address(0) and a fail-closed assertion: supply cap equal to total supply, no transfer or mint policies, and no admin, mint, burn, pause, or operator role for anyone. The token is admin-less from birth — a protocol fact recorded in the creation transaction, not a promise that someone renounced something later.

The full 1B supply was minted straight into the launch pool's single-sided seed — nobody, including the creator, held a token before the first buy. The main venue is the Uniswap v4 native-ETH launch pool 0x215b21…5a30ba, whose seed liquidity is owned by a hook with no removal code path.

A B20 token's balances live in Base's native state, and its contract bytecode is a one-byte marker. Two consequences matter when you read third-party sites:

• Storage-reading explorers under-count holders. They enumerate contract storage, which is empty here. This site instead folds the complete Transfer log and reconciles it wei-exact against balanceOf — the methodology explains the proof.
• Fork-simulators falsely flag it as a honeypot. Their forks read zero balances, so every simulated sell fails. Real sells settle on chain every day — the safety file pins actual sell receipts. The same logic cuts both ways: simulator-based "safe" badges are equally unreliable for B20.