ClankerCats Origin
ClankerCats is the first Mirage Garden anchor community. Before Mirage Garden became a public soToken foundry and marketplace, the project started with 200 on-chain pixelcats, CCAT identity, and the first proto-BOA experiment on Base.
PixelCats as proto-BOA
PixelCats proved the important idea: a Base community can use token-linked on-chain objects without following the normal ERC-721 NFT pattern.
PixelCats/CCAT uses custom ownership reads and custom transfer behavior. It is closer to the UniPeg-style idea than the old Factory-era ERC-721 collections were.
Why it matters now
Proper Mirage soTokens return to this lineage:
token balance supports object capacity
object ledger tracks specific IDs
specific transfer moves object + backing interval
PixelCats remains historically important because it showed that Mirage-native object ownership can exist outside standard NFT wallet assumptions.
Source review
The reviewed ClankerCats PixelCats flow reads ownership with custom paginated calls, not ERC-721 inventory calls:
OwnerUpegsPage(owner, page, pageSize) -> id + seed
renderer.tokenURI(id, seed) -> metadata/image
That is the practical reason PixelCats is the proto-BOA reference. It is a custom object ledger with renderer seeds. It is not a normal ERC-721 collection that a marketplace can settle with transferFrom.
PixelCats versus soTokens
| PixelCats / CCAT | Mirage soToken |
|---|---|
| Original custom Base experiment | Public factory for new communities |
| Custom CCAT ownership registry | Standardized LOA/BOA ledger interface |
| PixelCat-specific renderer and reads | Pluggable renderer and seed modules |
| Not normal ERC-721 marketplace inventory | Mirage-native marketplace |
| Proto-BOA root | Proper reusable soToken protocol |