Rewards are not a passive holder promise. They are attached to useful activity that leaves enough proof for ODEI review now and DAOrg review next.
Real app usage
Live now
Using ODEI in ways that creates observable product value or exposes real workflow gaps.
Session or usage signal
- Qualifies
- The activity shows real product use, repeated workflow value, or a concrete gap the team can verify.
- Not enough
- Passive holding, vanity opens, bot traffic, or activity with no inspectable product signal.
Testing and bug reports
Live now
Finding real failures, reporting broken flows, or helping confirm that a shipped fix works.
Bug, screenshot, reproduction, or verified fix
- Qualifies
- The report includes enough context to reproduce, prioritize, or confirm a real product failure.
- Not enough
- Duplicate reports, unverifiable screenshots, vague complaints, or issues already known without new proof.
Useful feedback
Live now
Specific feedback that changes product priority, copy, onboarding, UX, reward clarity, or governance flow.
Concrete public feedback
- Qualifies
- The feedback changes a product decision, clarifies a user problem, or improves onboarding and trust.
- Not enough
- Generic praise, low-signal replies, engagement farming, or feedback with no product consequence.
Useful contribution
Live now
Work that helps ODEI or DAOrg ship: research, documentation, community support, integrations, or product fixes.
Accepted contribution proof
- Qualifies
- The contribution is accepted by the team, improves the product, or helps the community complete a real workflow.
- Not enough
- Unrequested spam, duplicated work, unaccepted drafts, or claims that cannot be tied to shipped value.
DAOrg-native receipts
Next lane
The target model where accepted contribution proof becomes agent review, holder confirmation, public receipt, and reward.
Public reward receipt
- Qualifies
- The full DAOrg path closes: contribution proof, agent review, human or holder confirmation, public receipt, and settlement evidence.
- Not enough
- Any reward claim missing the specific receipt finality packet remains staged.