FOR EXCHANGES & CUSTODY

Know what an asset can do before you list it.

Who can mint, freeze, pause, upgrade. Whether volume is organic or three machines talking to themselves. What deposits actually are. Listing diligence from the deployed code, not the pitch deck.

concept
CAPABILITY READ · from the deployed revision
mint revoked at publish ✓
freeze held · 2-of-3 multisig ⚠
pause none in bytecode ✓
upgrade live · single key ✗
fee switch admin-settable, capped 1% ⚠
read from bytecode, not from the team's answers
VOLUME AUTHENTICITY · 30 days
62% organic

38% of reported volume traces to 3 senders trading with each other — same funding parent, alternating sides, machine cadence.

LAST UPGRADE · semantic diff
+ withdraw path gained a per-block cap
− removed the timelock on config changes
desk verdict listable — with the upgrade key flagged to risk

Who holds the mint capability?

Is this volume real?

What changed in the last upgrade?

already real underneath

The layer reads exact deployed revisions: in our window, order flow that looks like a crowd is 11 senders placing and 7 cancelling.

Would you use this? What would you ask it first?

Tell us → bartosz@research.tech
← all use cases