Database validation bounty program #2691
Replies: 5 comments 6 replies
Hi, @ArseniiPetrovich, Having joined the Chain.Love database program for more than 240 days, I think I am qualified to apply for the validation program. I therefore apply to be a validator. Thank you. |
|
Absolutely, @Adisaok :) |
dear maintainer, I have been participating in the chain.love database contribution program since December 2025. I am interested in participating In the validator program now. Faithfully, |
|
Welcome! |
Validator assignment thread: @harunsulaimanCurrent assignment: Assigned: 2026-09-07 20:11 UTC. Please independently verify the changes according to the validation requirements and submit your review within 72 hours. Future assignments and completion notes for @harunsulaiman should be posted as replies in this thread. |
Validator assignment thread: @AdisaokCurrent assignment: Assigned: 2026-09-08 06:13 UTC. Please independently verify the changes according to the validation requirements and submit your review within 72 hours. Future assignments and completion notes for @Adisaok should be posted as replies in this thread. |
|
Specifically in August our 2 validators reviewed 53 PRs. Some of them are still a subject of further compensation, as said PRs are not merged yet.
After initial conversation within a team we feel like neither compensation structure feels right, as simply acknowledging all PRs means neglecting the higher quality Adisaok currently has, but gating all the PRs means rewarding too low for the work that has been performed. Thus, final compensation for August for the already merged PRs will look the following way:
We believe that with proper further training the quality of both reviewers will improve, and increasing the rewards as a gesture of a good will. |
|
Thank you for the clarification and for the recognition. I really appreciate the team’s decision and the goodwill behind the revised August compensation. I also appreciate the feedback on review quality. I’ll continue focusing on making each validation more rigorous and consistent, particularly around canonical offer resolution, inherited fields, network-specificity, product lifecycle, evidence verification, and the current Chain.Love data model. The goal for me is not simply to complete more reviews, but to make the reviews increasingly accurate, reproducible, and useful to the project. Thank you again for the opportunity and for the continued training and feedback. |
|
Dear maintainer @ArseniiPetrovich Thank you for this initiative to give room for improvement. As a validator, I can truly tell you that the last 3weeks of working on this program really improved my validation skills. This in turn, proved that I can do much better review over time learning from the past reviews. I am now committed to ensuring the quality of my validation across all domains. I also thank @eugene17kotov for his considerate validation review. He consistently points out the particular misses and other errors we didn’t see or know about, including suggestions for future improvements. He has been so helpful throughout. I thank the team for the Rewards. I am now focused on ensuring that every review gets increasingly accurate and useful. Muchos Gracias, |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Validation Bounty Pilot
The Chain.Love database has grown significantly, and the number of contributions now exceeds what the core team can review promptly. We are therefore launching a pilot bounty for experienced contributors who help validate database pull requests. The objective is to reduce merge time while maintaining the quality of the database.
Becoming a validator
Validation bounty is not automatically available to every contributor.
To apply, a contributor must:
The list of approved validators will be public. Chain.Love may accept, reject, suspend, or remove validators based on their review quality.
Eligible pull requests
A PR can enter the validation queue only when:
DBIPs and other issues/proposals remain subject to core-team review for now.
Assignment
Review requirements
A compensated review must be submitted as a GitHub comment to a PR and must include:
Change requests must identify the exact file, row, and field involved and explain why the value is incorrect. Each blocking finding must include supporting evidence. Style preferences, optional improvements, and unsupported suspicions should be submitted as non-blocking comments and should not be treated as change requests.
Compensation
Approvals and change requests receive the same reward. Reviewers are compensated for validation work, not for producing a particular verdict.
For the duration of this pilot program we will assume the following rewards, based on number of cells changed in the reviewed PRs:
One bounty covers the initial review and one follow-up after requested corrections. A material expansion of PR scope may become a new validation task only when approved by @USS-Supervisor.
A review becomes payable when:
Quality control
The first ten reviews from every new validator will be audited by the core team.
After completing ten accurate reviews without a material miss, the contributor may become a trusted validator. Trusted reviews will be audited randomly instead of being fully repeated.
Pilot period
The program will initially run for 1 month (from 17.08.2026 to 17.09.2026). After the pilot, Chain.Love will evaluate the results of the program and adjust rates, limits, eligibility, and audit requirements.
Approved validators
@Adisaok
@harunsulaiman
All reactions