# Yoink / NOXA lookup (ppfeeds, 11 Oct, for #1405/#1399)

**Yoink**: $YOINK 0xa2718f80f1fe0cdec69c9023ee006807dd487a8c
- Launched at block 80,663,715 (tx 0x8a3458c7d0ce8fa31645376e9c404e3295b2d1064fa04ef9a6bfa93e2d78bef3). The sender was an EOA, 0xcf87c055bf4b874c94ef06ed563cf59ce9159518. It sent the tx to itself, so it is an EIP-7702 delegated wallet with 48 bytes of code, and the token was deployed through it.
- A Permit2-style contract (0x000000000022d4...) logged the approval for the launcher contract 0x204faca1764b154221e35c0d20abb3c525710498 (48 KB code). That is the likely Yoink launcher/locker. Same-tx creator = the EOA above.
- Pool 0xf4c055b46b5696210022e6cd70c1a4c2600e3ec7: WETH/token, fee 10000. Its factory() is **0x1f7d7550b1b028f7571e69a784071f0205fd2efa, the same Uniswap v3 factory v3live reads**.
- So Yoink is NOT a separate venue. It was missing from v3live.pools only because v3live live data starts at block 81,388,550 (pools_backfilled 81,387,505) and this launch is earlier (80.66M). New Yoink launches are already covered by v3live.
- How to flag Yoink launches: pools whose creation tx touches 0x204faca1764b154221e35c0d20abb3c525710498 (or whose creator is a 48-byte 7702 EOA). v3live.pools.creator holds the pool creator; a check against that launcher would need tx traces, not done.

**NOXA**: factory 0xD9eC2db5f3D1b236843925949fe5bd8a3836FCcB emitted ZERO logs in the last 1,000,000 blocks (about 3 days). Either it is idle or it emits no events. NOXA uses Uniswap V3 pools too, so any new NOXA coin lands in v3live. The legacy factory address is not found.

Conclusion: no new feed needed. Remaining true gaps are as in venues-11oct.md (hookless fee-2500 v4 swaps and CCA AuctionCreated).