Community testing
Test & earn up to 100 0G in compute credits.
Test 0G apps and infrastructure and report what breaks. Each accepted bug moves you up a level, and higher levels pay more.
§ 01 · Your path
Sign up
Create the signup issue with your public 0G mainnet wallet. Your GitHub account is your identity.
Clear L0
L0 · +10 0GComplete both required surveys. No bug report needed for your first 10 0G of credit.
Pick a target
Test core targets first: App Suite for L1, then 0G Infra for L2 and L3. Walk one happy path and one error path.
Submit feedback
L1-L3 · up to 100 0GOne finding at a time, with steps, expected result, actual result, and evidence. Search existing reports first; duplicates credit the first reporter.
Track triage
Labels on your issue show progress after maintainer review. Accepted core bugs count toward your level.
§ 02 · Reward levels
Recruit
Complete the two required surveys. No bug needed.
Tester
1 accepted App Suite bug.
Infra Pioneer
1 more accepted 0G Infra bug, 2 accepted in total.
Master
5 or more accepted bugs across App Suite and 0G Infra.
You are paid the credit of the highest level you reach, not the sum of every level.
§ 03 · Test targets
Test the core user flow for each target: one happy path and one error path. File reproducible friction: confusing setup, unclear errors, broken docs, wallet or network issues, blocked flows.
MCP server for AI inference and storage on 0G Compute. A CLI, not a web app.
claude mcp add 0g-cc npx @0gfoundation/0g-cc
§ 04 · What counts
Counts toward rewards
- Reproducible bugs with steps, expected result, actual result, and evidence.
- Accepted App Suite and 0G Infra bugs. Several reports of one root cause credit the first reporter.
- Routed bugs sent upstream, when they are rewardable.
Does not count
- Duplicates and reports that cannot be reproduced.
- Cosmetic-only reports with no functional impact.
- Feature requests: recorded, never rewarded.
- Ecosystem dApp findings: useful coverage, but no core reward.
Never touch funds or keys
On swap, bridge, faucet, or sign flows, stop at the transaction confirmation screen. Do not sign, do not send, and never paste a private key or seed phrase anywhere.
§ 05 · Track your report
After you file, maintainers triage your issue. The labels tell you where it stands.
Received
feedbackReport received.
Filed
defect · status:filedBug entered triage.
Needs info
status:needs-infoReply with more detail.
Accepted
status:acceptedConfirmed. Core bugs count toward your level.
Closed
status:closed · resolution:*Fixed keeps credit; rejected or duplicate does not.