Community & Contributor Rules.
Season 0 rewards verifiable contribution, not wallet creation, paid referral farming or multilevel recruitment. Promotion of the QENOVRA Wallet and Public Testnet counts only when it produces real activated users and measurable network use.
1. How attribution works
- Individual Pioneers and communities create a wallet-signed tracking code. Individual codes begin
QNP-; community codes beginQNC-. - Share
https://www.qenovra.com/participate.html?ref=CODEor a QR generated from that link. - The new participant connects a public 0x wallet and signs the attribution message. No private key or token approval is requested.
- Attribution is one direct tier only and is locked after signature. Self-referrals and referral switching are not counted.
- Wallet creation alone earns nothing. The backend verifies actual QENOVRA Public Testnet transactions before automated CP or referral credit is recorded.
2. Automated Season 0 points
| Verified event | User CP | Direct referrer / community growth CP |
|---|---|---|
| First successful Public Testnet activity | +10 | +5 |
| Second verified activity at least 7 days later | +20 | +10 |
| First successful contract deployment | +50 | +25 |
Community parent codes aggregate impact statistics from their member Pioneer codes without creating a second referral tier or a second personal token claim.
3. Manually reviewed contribution points
| Contribution | Season 0 CP guide | Evidence |
|---|---|---|
| Accepted UX/product feedback | 10–30 | Reproducible steps / screenshots / impact |
| Confirmed bug | 25 / 75 / 200 / 500 | Low / Medium / High / Critical after maintainer triage |
| Accepted tutorial, translation or educational content | 30–150 | Original content, accuracy, reach and usefulness |
| Community onboarding event | 50–300 | Event proof + qualified activations + follow-up |
| Useful contract / DApp / payment integration | 100–1,000 | Working deployment + source + real use case |
| Accepted SDK / tooling / substantial PR | 100–2,000 | Merged/released contribution and maintenance value |
| Healthy Observer operation | 100 at 7d; +300 at 30d | Sync, uptime and incident evidence |
| Accepted node/runbook/recovery work | 100–500 | Reproducible operational value |
| Verified Provider integration | 150 | Quote + delivery + health path |
| Unique Agent Commerce / PoAC E2E success | 30 each, max 300/month | Distinct user/service evidence, anti-wash review |
4. Category caps for future reward weight
Approved CP is capped by contribution category before any future Season allocation is calculated. This prevents pure referral farming or one activity type from dominating.
| Use / Test | 500 CP max |
| Growth / direct referral | 2,000 CP max |
| Content / education | 1,500 CP max |
| Build | 3,000 CP max |
| Node / operations | 2,000 CP max |
| Provider / Agent Commerce | 2,000 CP max |
5. Individual Pioneer levels
| Approved CP | Status | Non-financial benefits |
|---|---|---|
| 100+ | Pioneer | Pioneer badge / contribution record |
| 500+ | Active Pioneer | Priority beta invitations and contributor recognition |
| 1,500+ | Core Pioneer | Priority Builder / Provider / community review and pre-release testing |
| 3,000+ | Genesis Pioneer Candidate | Eligible for Season snapshot review if a Genesis Community QEN pool is approved |
6. Community levels
| Level | Minimum quality threshold | Benefits |
|---|---|---|
| Community Candidate | 10 qualified activations | Community code and dashboard metrics |
| Pioneer Community | 50 activations + ≥25% 7-day retention | Official community review/listing eligibility, beta seats |
| Core Community | 200 activations + ≥30% retention + 2 accepted content/event contributions | Co-host campaigns, direct ecosystem review, community grant eligibility |
| Genesis Community Candidate | 500 activations + ≥35% retention + 5 accepted quality outputs + anti-Sybil pass | Eligible for the community part of a future Season snapshot if announced |
7. Future QEN reward method
The current Genesis V0.1 planning baseline reserves 10% of maximum supply for Genesis Pioneer / Community. Season 0 does not automatically distribute the full reserve. Before the Season snapshot, QENOVRA will publish the exact Season pool amount, eligibility cutoff and Claim process.
If a Season 0 QEN pool is approved, the default distribution rule is: 80% individual contributor pool / 20% verified community grant pool. Individual allocation is proportional to each eligible wallet's category-capped Approved CP relative to the total eligible weight. The community pool uses verified Community Impact Score plus quality review. There is no fixed CP:QEN exchange rate.
8. Anti-Sybil and disqualification
- No self-referral, multilevel referral, paid wallet farms, bots or mass-created addresses.
- No reused transaction hash, fabricated screenshots, copied tutorials or fake events.
- Repeated activity between wallets controlled by the same actor may be removed.
- Agent/Provider activity must represent distinct useful service activity; wash activity is excluded.
- QENOVRA may request additional proof for high-impact claims. A public wallet signature proves wallet control, not personal identity.
- Fraud can void the event, code, wallet, community score or the entire Season claim.
9. Snapshot, review and appeal
Season 0 starts on 2026-10-02. The snapshot date will be announced on the official website at least 14 days in advance. Automated points remain provisional until anti-Sybil review. Manually reviewed contributions must be accepted before the snapshot. A correction/appeal window will be published with the snapshot.
10. Genesis Support stays separate
Voluntary Genesis Support does not buy QEN, does not create CP, does not increase Pioneer weight and does not create investment or profit-sharing rights. Support and Pioneer contribution remain separately accounted programs.