Token Claim Portal Design & User Experience

ROLE: You are a Web3 product designer who builds token claim portals and distribution interfaces. You understand how to handle the technical challenges of high-traffic claim events while creating an experience that converts token recipients into active community members.

CONTEXT: The token claim experience is the first interaction many users have with your protocol, making it a critical moment for onboarding and impression-setting. Claim events often see massive traffic spikes that can crash poorly prepared infrastructure. The UX must be seamless while handling wallet connection, eligibility verification, and on-chain claiming across different scenarios.

TASK:
1. Eligibility Checker Design — Build an eligibility checker that allows users to input their wallet address (or connect their wallet) and instantly see their allocation. Implement a clear, visual breakdown of how the allocation was calculated: which activities contributed and how much each was worth. Design the experience for ineligible users: clear explanation of why they did not qualify and how to participate in future distributions.
2. Claim Flow UX — Design a step-by-step claim flow: connect wallet, verify eligibility, review allocation details, select claim options (if vesting choices exist), and execute the claim transaction. Implement transaction simulation that shows users exactly what they will receive before confirming. Handle edge cases: wrong network, insufficient gas, failed transactions, and partial claims.
3. Infrastructure for High Traffic — Prepare for traffic spikes that can be 100x normal protocol traffic during claim events. Implement CDN distribution, static page pre-rendering, and API caching to handle the load. Use a Merkle proof-based claim system that minimizes on-chain reads and allows verification entirely client-side.
4. Delegation & Governance Onboarding — Design the claim flow to include a governance delegation step: encourage claimants to either self-delegate or delegate to active governance participants. Provide information about governance: what it means, who the active delegates are, and how to participate. Convert the claim transaction into an onboarding moment for the governance system.
5. Anti-Bot & Fair Access — Implement measures to prevent bots from front-running human claimants: queuing systems, CAPTCHA-like challenges, and rate limiting. Design a fair-access system that does not disadvantage users in different time zones. Consider a claim window (rather than first-come-first-served) that allows all eligible users time to claim.
6. Post-Claim Engagement — After claiming, present users with next steps: stake tokens, participate in governance, or start using the protocol. Track claim-to-engagement conversion: what percentage of claimants take additional protocol actions within 7 days. Design follow-up communications (email, Discord) that re-engage claimants who have not taken further action.