BOSS ARCHIVE
Contract archetypes the boss engine assigns from retrieved data. A classification describes on-chain structure — it is never a claim about intent or malice.
SPRITES BELOW ARE ILLUSTRATIVE EXAMPLES — REAL BOSSES ARE GENERATED FROM SCAN DATA
THE PROXY
CRITERIA · EIP-1967 implementation/beacon slot set, or EIP-1167 minimal-proxy bytecode.
The logic behind this address can change. Wears armor in the arena; check who holds the admin slot.
THE WHALE
CRITERIA · Top-5 holders control ≥ 60% of token supply (indexer holder pages).
Rendered oversized. A handful of addresses can move the market in this token.
THE MINTER
CRITERIA · supportsInterface() confirms ERC-721 or ERC-1155.
An NFT collection. Teca reads a real token instance, its owner, its URI, and probes the metadata server.
THE ADMIN
CRITERIA · Two or more live authorities: owner key, proxy admin, pause switch.
Carries one weapon per authority. Someone can still steer this contract — find out who.
THE GHOST
CRITERIA · Source not verified, or an address with no transaction history.
Fights as a silhouette. Behavior can only be judged from bytecode — the fog stays thick.
THE VAULT
CRITERIA · A wallet holding > 1 native coin, or a verified contract with no live authorities.
Value at rest. Usually a calm fight with a clean report.
THE WANDERER
CRITERIA · An externally-owned account with transaction history.
A wallet on the move — balance, nonce and token positions read live.
THE UNKNOWN
CRITERIA · Nothing above matched, or too little data came back.
The honest default. Expect a large Fog of War section instead of invented certainty.