How it works
[ Verification before claim ]
The flow keeps visible actions simple while moving trust-sensitive state to route handlers and PostgreSQL.
Connect wallet
A nonce is signed by the wallet and verified on the backend with viem.
Complete X actions
Open the project profile and prepared referral post from the dashboard.
Store task state
Task clicks are saved by route handlers and used to unlock eligibility.
Claim on Base
The user calls the claim contract directly and pays gas from their own wallet.
Token allocation
ORIXYS distribution snapshot.
Replace these values with final tokenomics when the contract and Merkle root are ready.
Claim pool
Community first
Referral layer
Attribution ready
Claim control
User signed
Referral
Invite flow is built in.
Each authenticated wallet receives a code and shareable link. Referral source is stored in a secure cookie and attached during wallet verification.
FAQ
[ Launch notes ]
Can the frontend mark a user as eligible?
No. Eligibility is written by backend route handlers after wallet auth and social task clicks.
Who pays gas for claim?
The connected wallet sends the contract transaction and pays gas on Base.
Does this need X API keys?
No. The MVP opens X links and marks tasks complete after the user clicks them.
Where does the claim proof come from?
The MVP returns an empty proof placeholder. Replace it with a Merkle proof service before production.