Submission Process

What this is

This is the canonical five-step submission workflow used for every claim.

  ┌──────────┐   ┌──────────┐   ┌──────────┐   ┌──────────┐   ┌──────────┐
  │ STEP 1   │──→│ STEP 2   │──→│ STEP 3   │──→│ STEP 4   │──→│ STEP 5   │
  │ Connect  │   │ Tweet    │   │ Receipt  │   │ Review   │   │ Gates    │
  │ Wallet   │   │ Verify   │   │ Upload   │   │ Confirm  │   │ Progress │
  └──────────┘   └──────────┘   └──────────┘   └──────────┘   └──────────┘

How it works

1. Connect wallet — establish payout address and tier context
2. Verify tweet — validate social proof and timing requirements
3. Upload receipt — provide legible physical receipt evidence
4. Review and submit — confirm payload before finalization
5. Track gate progress — monitor pass/fail and queue states

Common failure patterns

• Reused receipts or stale tweets from older attempts
• Unreadable wallet characters on receipt images
• Cooldown not expired for tier/account policy

Operator note

Use a new compliant receipt and valid tweet context for each attempt. Start at /submit.