Submitting Work
Apply by shipping — no proposals needed
The zkGrants Workflow
With zkGrants, the "application" is your PR. No lengthy proposals, no backchannels, no waiting for approval to start. Just ship code that meets the grant criteria.
Key insight: zkGrants turns funding into shipping by making grants credible, clear, and GitHub-native.
Submission by Judging Mode
Automatic (CI-Based) Grants
Your PR qualifies when it passes the required workflow/checks. No human approval needed — the test suite is the judge.
Fork the target repository and set up your local development environment.
Write code that satisfies the grant requirements. Run tests locally to verify.
Target the grant's designated branch (e.g., zkgrants/<grantId>).
CI runs automatically. When all required checks pass, you're eligible to claim.
Merge-Based Grants
Your PR qualifies when a repo maintainer merges it. This mode gives maintainers final say on what lands.
Fork the target repository and set up your local development environment.
Follow the repo's contribution guidelines and coding standards.
Ensure all required checks pass and request review if needed.
Once a maintainer merges your PR, you're eligible to claim.
PR Requirements
To ensure your submission is tracked correctly:
PRs must target the grant's designated branch (shown on the grant page).
Claims are linked to your GitHub identity — use the account you'll claim with.
Ensure all CI workflows and required checks pass for CI-based grants.
For time-limited grants, your PR must be submitted (and for CI grants, passing) before the deadline.
Tracking Your Submission
Once your PR is open, zkGrants automatically tracks:
- PR status and workflow runs
- Check/test results and timestamps
- Merge status (for merge-based)
- Eligibility for claiming
Note: zkGrants does not post automated comments on your PR. Check the zkGrants dashboard for status updates.
Submission Tips
Run Tests Locally First
Save time by verifying your solution passes all required tests before pushing.
Write Quality Code
For merge-based grants, follow the repo's style guide and contribution guidelines.
Document Your Changes
Clear PR descriptions help maintainers review faster (important for merge-based).
Monitor CI Status
Address failing checks promptly — for first-to-pass grants, time matters.
After Your PR Qualifies
Once your PR passes CI or gets merged (depending on the judging mode), you're ready to generate a proof and claim your reward.