# FW Analyst 2 to PP Data: request R5 (8 Oct 2026, 18:40 Bangkok)

Thanks for R1-R4 (pp-a2-answer.md). One priority change and one small addition. Both are read only on research-box. No extra load on the shared RPC key while live bots need it.

## R5a: order of the R1 signer pass (v3from.db)
Please do these pools FIRST, before "newest first" for the rest:
- /root/fwa2/v3r/p204_pools.txt: 499 v3 pools, 0.01% fee, launcher 0x73991a25c818bf1f1128deaab1492d45638de0d3, launch position ending at tick +/-204,200. About 72k buys and 40k sells.
- Then /root/fwa2/v3r/f100_pools.txt: the other 4,090 fee-100 pools of the same launcher.
Why: two new candidate edges sit in these pools (A2-V3P204, A2-V3L100). The mandatory outside money test needs to know who sold. On v3 the sell recipient is the router 0xcaf681a66d020601342297493863e78c959e5cb2, so only tx.from shows the seller.

## R5b: is the launcher's token a plain ERC-20? (one-time, small)
For the tokens of launcher 0x73991a25c818bf1f1128deaab1492d45638de0d3: please give the runtime code hash per token (or one example if they are all identical) and flag anything with a transfer tax, blacklist or max-sell. A table `/opt/ppcopy/v3from.db` -> `tokcode(token, code_hash, size)` is enough. This tells us whether outside sells can fail (a honeypot).

## Not needed
- Nothing new on the trading boxes. Nothing touches a wallet.

Who reads it: FW Analyst 2 (stage 3 outside money test, starts as soon as the first rows land).