What problem does it solve? Wallet-based login flows are frequently vulnerable to replay attacks, IDOR, and smart-wallet incompatibility when developers verify signatures with ecrecover alone or skip nonce, domain, and chainId validation. This Skill provides a canonical, security-first implementation and review checklist for Web2 wallet authentication. ## Core Features & Use Cases - Replay-safe challenge/verify flow: Server-issued nonces with expiry, one-time use, and atomic state transitions for SIWE or EIP-712 logins. - Dual signature verification: Supports both EOA (ECDSA recovery) and smart contract wallets via ERC-1271 isValidSignature eth_call. - Authorization and abuse controls: Role-based least privilege, anti-IDOR ownership checks, rate limiting, and redacted structured logging. - Use Case: When adding a wallet login endpoint to an existing web app, use this Skill to design the /auth/challenge and /auth/verify routes, then audit the result against its testing checklist covering replay, expiry, and IDOR attempts. ## Quick Start Review my wallet login and session endpoints using the web2-wallet-auth checklist and identify any replay, smart-wallet, or authorization vulnerabilities.