How to Participate
Community tester guide — explore prototypes, file feedback, and earn recognition
Open to Everyone
Anyone in the Autheo community can participate as a tester. No special permissions or prior approval required — just a willingness to explore and provide honest feedback.
How to Start Testing
Browse active prototypes
Visit the Explore Prototypes page. Filter by status, risk level, or alignment tag to find prototypes that interest you. Start with Active–Experimental status.
Read the prototype README
Each prototype repo includes a detailed README explaining its purpose, hypothesis, known limitations, and testing instructions. Read it fully before testing.
Set up on testnet only
Clone the prototype repository and follow its setup instructions. All Labs prototypes run on Autheo testnet only — never use real assets or connect to mainnet.
Test and document findings
Explore the prototype and document what you find. Note: does it match the stated hypothesis? What works well? What breaks? Any unexpected behavior?
File structured feedback
Open a GitHub Issue on the prototype repository using the appropriate severity label (P0–P3). Include reproduction steps, environment details, and any screenshots or logs.
Join the community discussion
Share your experience in the #labs-feedback channel on Discord. Connect with other testers and the prototype lead.
Feedback Severity Levels
Use the correct severity label when filing a GitHub Issue. This helps the prototype lead triage and prioritize fixes.
Critical
Prototype cannot be used at all. Blocks all testing.
Major
Significant functionality is broken. Partial workaround may exist.
Minor
A workaround exists but quality is degraded. Testing can continue.
Enhancement
Nice-to-have improvement. Does not block testing or core functionality.
What Makes Good Feedback
- Reproduction steps: Numbered steps that reliably reproduce the issue from a fresh state.
- Expected vs. actual behavior: What did you expect to happen? What actually happened?
- Environment details: Browser, OS, wallet version, testnet configuration.
- Evidence: Screenshots, error messages, console logs, or video recordings.
- Hypothesis alignment: Does the prototype achieve what it claims in the README?
Tester Recognition
Community testers who contribute high-quality feedback are recognized in quarterly Labs transparency reports. Consistent, valuable contributors may be invited to participate in early access programs for graduating prototypes.
On-chain proof-of-participation features for testers are on the roadmap — tracked in GitHub Issue #4.