Step 01
Request a test allocation
Use the devnet app to request ETL during the airdrop-only test stage and direct it to the wallet you want to use.
Proof-of-flow campaign
Eeteel Claim Flow Challenge
Complete the full devnet flow and prove it with wallet activity. No backend points. No reward promise. Just on-chain proof that the protocol path works.
Campaign Task
Request. Stake. Wait. Claim. Verify.
The challenge is intentionally simple: complete the request-and-claim lifecycle on devnet, then share the transaction links that prove each step happened on-chain.
Step 02
Stake after approval
After the request is approved and ETL is received, move it into stake state so claim readiness can be tracked on-chain.
Step 03
Wait if pending
If the position is pending, wait for the protocol period that makes it claim-ready.
Step 04
Claim a funded asset
Claim only when a supported distribution asset is funded and the wallet is eligible.
What counts as proof
The campaign does not need off-chain scoring. Your proof is the public transaction history from the wallet that completed the flow.
- Wallet address used for the flow.
- Explorer link for the request or approval activity.
- Explorer link for the stake transaction.
- Explorer link for the claim transaction, when claim-ready.
- One short note about what was confusing or what broke.
Campaign boundaries
The challenge is a protocol test, not a financial promotion. Keep every public post clear about that boundary.
- No off-chain points database.
- No guaranteed token, airdrop, yield, or financial reward.
- No leaderboard unless it can be derived from public on-chain state.
- No claim that devnet activity has market value.
Suggested public post
I completed the Eeteel devnet flow: Request - Stake - Claim - Verify. The proof is in my wallet transactions. No points, no reward promise, just on-chain protocol testing.