chenjunfengandClaude Opus 5 48d61990cb gmgn-contract-dd: scope the EVM lock tightening to the six meme-native chains ...

Upstream added `arbitrum` and `hyperevm` (#227), making the file's chain counts
nine / eight rather than seven / six. Three things follow.

1. Chain counts in the passages this branch added still said six EVM chains and
   seven supported chains. Corrected, and the `burn_status: ""` coverage claim is
   extended with a 2026-09-11 measurement on the two new chains: ARB, WBTC, ODYS,
   SIGNAL, CPU and CHAMELEON all return `""`, so the burn half is missing there too.

2. The Step 3 tightening — deduct −12 and cap 79 on `lock_summary.is_locked ===
   false` alone — was calibrated on the six chains that existed then, where 12 of
   12 sampled tokens returned `is_locked: true`. It does not hold on the two new
   ones: measured 2026-09-11 on the top three of each chain's 24h trending list,
   ARB and WBTC on `arbitrum` and SIGNAL and CPU on `hyperevm` all return
   `is_locked: false` — 4 of 6, including the chain's own governance token and
   wrapped Bitcoin. Deep DEX liquidity from real market makers is not locked and
   is not meant to be, so there the deduction would fire hardest on the tokens it
   exists to clear. The row is now skipped on `arbitrum` and `hyperevm` and the
   tightening applies only to `bsc`, `base`, `eth`, `robinhood`, `arc`, `stable`.
   Cross-references in the cap summary, the cap-cause list and the Step 3 table
   row name the scope.

3. The two dated bsc trenches passages contradicted each other on the same
   180-row sample — 130 flap / 50 four.meme against flap 143 / fourmeme 37. The
   per-platform split is not a stable quantity: two captures of the same 180 rows
   hours apart on 2026-09-11 gave 150 / 30 and 137 / 43. The load-bearing claim is
   the mapping, not the mix, so the suffix passage now states the mapping with
   today's figures and says outright that a platform's share must not be read off
   one capture, and the non-load-bearing counts are dropped from the launchpad
   passage, whose actual claim is that `market trenches` never emits `openfour`.

No band boundary, weight or cap value changes. Inventory totals are unchanged at
23 on `sol` and 25 on the EVM chains — the skipped lock row stays in the
denominator as a skipped check.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-09-11 16:35:29 +08:00

..

SKILL.md

gmgn-contract-dd: scope the EVM lock tightening to the six meme-native chains

2026-09-11 16:35:29 +08:00