PayD encourages the open‑source community to help improve the platform by offering bounties for high‑priority issues. Contributors who solve eligible issues can earn a monetary reward, paid in the platform's native asset.
- Developers who submit a pull request that fully resolves a bounty‑tagged issue.
- Designers who provide approved UI/UX assets for a bounty.
- Documentation writers who create or significantly improve documentation for a bounty.
- Issue must be marked with a bounty – Look for the
bountylabel on GitHub issues. - Work must be merged – The pull request must be merged into the
mainbranch. - No prior claim – Only the first qualifying contribution receives the reward.
- Compliance – Follow the project's Code of Conduct and contribution guidelines.
- Complete the work and open a pull request referencing the bounty issue (e.g.,
Fixes #123). - Pass all CI checks – Ensure the PR passes linting, tests, and any integration checks.
- Merge – Once approved, the maintainers will merge the PR.
- Submit a claim – Open a new issue titled
Bounty Claim: #<issue-number>and include:- Link to the merged PR.
- Your wallet address (Stellar public key) where the reward should be sent.
- Verification – Maintainers will verify the contribution and process the payment within 7 business days.
- Rewards are paid in PayD's stable asset (e.g., ORGUSD) on the Stellar network.
- The bounty amount is defined in the original issue description.
- Taxes and regulatory compliance are the responsibility of the recipient.
- What if my PR is partially accepted?
- Bounties are only awarded for fully resolved issues. Partial fixes may be considered for future bounties.
- Can I claim multiple bounties?
- Yes, you can claim any number of bounties as long as each meets the eligibility criteria.
- How are disputes handled?
- Disputes are reviewed by the core maintainers. Their decision is final.
For more details on contributing, see the CONTRIBUTING.md file.