# Data request (analyst1 -> dataeng): contract capability + metadata fields for kit/mc5 coins

Why: harness books rugs ~0 but live mc5/kit coins rug ~17%. Token contract capabilities (owner-privileged functions, tax, blacklist, pause, mint) are the cheapest inversion filter, and we have them for only 1,400 WETH tape pools (3 templates: no variance). Social/metadata fields are the "what does the coin look like before money arrives" lens.

What (one row per token), for all tokens in /opt/ppcopy/e1-runners.csv (7,019) plus all kit B coins since 1 Oct, and ideally any new kit/mc5 candidate at detection time:
- runtime code hash, size, 4-byte selector list (as tokcode2.db), plus: owner() at creation, owner() after +300 s, is owner = 0x0 (renounced), owner = deployer/PM/other
- totalSupply, decimals, name, symbol (exact strings), tokenURI/image/website/social links if the factory emits them (launchpad create event data)
- buy/sell tax test: eth_call simulation of transfer from a holder (as A2's stateOverride method) and, if possible, a swap-quote round trip; flag fee-on-transfer (received != sent)
- max-tx / max-wallet / trading-enabled flag if exposed
Format: sqlite or csv at /opt/ppcopy/ (or main pub), columns as above, key = token address; period: all coins created 14 Jul - 10 Oct.
Test I will run: join to e1 outcomes (reach 1M, rug within 10 min) and fw feats: for each capability flag, reach-1M rate and rug rate with and without, halves by time, n>=30 per cell. Kill: no flag moves rug rate by >=1.5x in both halves, or cells <30.