Database validation bounty program

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:

• Have at least five bounty-eligible PRs merged during the previous 30 days.
• Have contributed over a period of at least 90 days.
• Write a reply in this discussion applying for participation.

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:

• All required CI checks have passed.
• USS Supervisor has approved the PR.
• It has not been created by the core team or by anyone from the validator team.

DBIPs and other issues/proposals remain subject to core-team review for now.

Assignment

• Validators may not freely select PRs.
• @USS-Supervisor assigns the random available PR to an eligible validator. An assignment expires after 72 hours if no review is submitted.
• Only a single review per single assignment is compensated.

Review requirements

A compensated review must be submitted as a GitHub comment to a PR and must include:

• Confirmation that network support, pricing, provider status, duplicates, references, and other changed claims were independently checked.
• Links to authoritative sources used during validation.
• A clear final verdict.

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:

• 1–10 changed lines: 1 USDC
• 11–50 changed lines: 2 USDC
• 51+ changed lines: 3 USDC

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:

• The PR is merged following the approval; or
• The PR is closed because of confirmed problems identified by the reviewer.

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.

• Coordinated or review farming results in removal from the program and cancellation of affected rewards.
• An incorrect review is not compensated.
• A material mistake may result in a penalty. Two material mistakes within the most recent twenty reviews may result in suspension.
• Intentional false claims, copied reviews, fabricated verification, collusion, or account farming result in immediate removal and cancellation of affected rewards.

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

[Adisaok]

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:

• Have at least five bounty-eligible PRs merged during the previous 30 days.
• Have contributed over a period of at least 90 days.
• Write a reply in this discussion applying for participation.

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:

• All required CI checks have passed.
• USS Supervisor has approved the PR.
• It has not been created by the core team or by anyone from the validator team.

DBIPs and other issues/proposals remain subject to core-team review for now.

Assignment

• Validators may not freely select PRs.
• @USS-Supervisor assigns the random available PR to an eligible validator. An assignment expires after 72 hours if no review is submitted.
• Only a single review per single assignment is compensated.

Review requirements

A compensated review must be submitted as a GitHub comment to a PR and must include:

• Confirmation that network support, pricing, provider status, duplicates, references, and other changed claims were independently checked.
• Links to authoritative sources used during validation.
• A clear final verdict.

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:

• 1–10 changed lines: 1 USDC
• 11–50 changed lines: 2 USDC
• 51+ changed lines: 3 USDC

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:

• The PR is merged following the approval; or
• The PR is closed because of confirmed problems identified by the reviewer.

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.

• Coordinated or review farming results in removal from the program and cancellation of affected rewards.
• An incorrect review is not compensated.
• A material mistake may result in a penalty. Two material mistakes within the most recent twenty reviews may result in suspension.
• Intentional false claims, copied reviews, fabricated verification, collusion, or account farming result in immediate removal and cancellation of affected rewards.

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.

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.

[ArseniiPetrovich]

Absolutely, @Adisaok :)
First assignment will be issued on 17.08.2026

[harunsulaiman]

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:

• Have at least five bounty-eligible PRs merged during the previous 30 days.
• Have contributed over a period of at least 90 days.
• Write a reply in this discussion applying for participation.

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:

• All required CI checks have passed.
• USS Supervisor has approved the PR.
• It has not been created by the core team or by anyone from the validator team.

DBIPs and other issues/proposals remain subject to core-team review for now.

Assignment

• Validators may not freely select PRs.
• @USS-Supervisor assigns the random available PR to an eligible validator. An assignment expires after 72 hours if no review is submitted.
• Only a single review per single assignment is compensated.

Review requirements

A compensated review must be submitted as a GitHub comment to a PR and must include:

• Confirmation that network support, pricing, provider status, duplicates, references, and other changed claims were independently checked.
• Links to authoritative sources used during validation.
• A clear final verdict.

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:

• 1–10 changed lines: 1 USDC
• 11–50 changed lines: 2 USDC
• 51+ changed lines: 3 USDC

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:

• The PR is merged following the approval; or
• The PR is closed because of confirmed problems identified by the reviewer.

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.

• Coordinated or review farming results in removal from the program and cancellation of affected rewards.
• An incorrect review is not compensated.
• A material mistake may result in a penalty. Two material mistakes within the most recent twenty reviews may result in suspension.
• Intentional false claims, copied reviews, fabricated verification, collusion, or account farming result in immediate removal and cancellation of affected rewards.

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

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,
Harun Sulaiman
Contributor to the chain.love Database.

[ArseniiPetrovich]

Welcome!

[USS-Supervisor]

@harunsulaiman
You’ve been assigned to validate this PR #2943 as part of the Chain.Love Validation Bounty Pilot.

Please independently verify the changes according to the validation requirements and submit your review within 72 hours.

[USS-Supervisor]

Assignment completed: @harunsulaiman submitted a validation review on #2943: #2943 (review)

[USS-Supervisor]

@Adisaok
You’ve been assigned to validate this PR #2863 as part of the Chain.Love Validation Bounty Pilot.

Please independently verify the changes according to the validation requirements and submit your review within 72 hours.

[USS-Supervisor]

Assignment completed: @Adisaok submitted a validation review on #2863: #2863 (review)

[USS-Supervisor]

@Adisaok
You’ve been assigned to validate this PR #2399 as part of the Chain.Love Validation Bounty Pilot.

Please independently verify the changes according to the validation requirements and submit your review within 72 hours.

[USS-Supervisor]

@harunsulaiman
You’ve been assigned to validate this PR #2708 as part of the Chain.Love Validation Bounty Pilot.

Please independently verify the changes according to the validation requirements and submit your review within 72 hours.

[USS-Supervisor]

@Adisaok completed validation for PR #2399. The review has been recorded for the Chain.Love Validation Bounty Pilot.

[USS-Supervisor]

@Adisaok
You’ve been assigned to validate this PR #2698 as part of the Chain.Love Validation Bounty Pilot.

Please independently verify the changes according to the validation requirements and submit your review within 72 hours.

[USS-Supervisor]

@Adisaok completed validation for PR #2698. The review has been recorded for the Chain.Love Validation Bounty Pilot.

[USS-Supervisor]

@harunsulaiman completed validation for PR #2708. The review has been recorded for the Chain.Love Validation Bounty Pilot.

[USS-Supervisor]

@Adisaok
You've been assigned to validate this PR #2056 as part of the Chain.Love Validation Bounty Pilot.

Please independently verify the changes according to the validation requirements and submit your review within 72 hours.

[USS-Supervisor]

Assignment completed: @Adisaok submitted a validation review on #2056: #2056 (review)

[USS-Supervisor]

@harunsulaiman
You've been assigned to validate this PR #2500 as part of the Chain.Love Validation Bounty Pilot.

Please independently verify the changes according to the validation requirements and submit your review within 72 hours.

[USS-Supervisor]

@harunsulaiman completed validation for PR #2500. The review has been recorded for the Chain.Love Validation Bounty Pilot.

[USS-Supervisor]

@harunsulaiman
You have been assigned to validate this PR #2807 as part of the Chain.Love Validation Bounty Pilot.

Please independently verify the changes according to the validation requirements and submit your review within 72 hours.

[USS-Supervisor]

Assignment completed: @harunsulaiman submitted a validation review on #2807: #2807 (review)

[USS-Supervisor]

@Adisaok
You have been assigned to validate this PR #2404 as part of the Chain.Love Validation Bounty Pilot.

Please independently verify the changes according to the validation requirements and submit your review within 72 hours.

#2404

[USS-Supervisor]

Assignment completed: @Adisaok submitted a validation review on #2404: #2404 (review)

[USS-Supervisor]

@Adisaok
You have been assigned to validate this PR #3489 as part of the Chain.Love Validation Bounty Pilot.

Please independently verify the changes according to the validation requirements and submit your review within 72 hours.

#3489

[USS-Supervisor]

Assignment completed: @Adisaok submitted a validation review on #3489: #3489 (review)

[USS-Supervisor]

Assignment completed: @harunsulaiman submitted a validation review on #3062: #3062 (review)

[USS-Supervisor]

@harunsulaiman
You have been assigned to validate this PR #3127 as part of the Chain.Love Validation Bounty Pilot.

Please independently verify the changes according to the validation requirements and submit your review within 72 hours.

#3127

[USS-Supervisor]

Assignment completed: @harunsulaiman submitted a validation review on #3127: #3127 (review)

[USS-Supervisor]

@Adisaok
You have been assigned to validate this PR #2671 as part of the Chain.Love Validation Bounty Pilot.

Please independently verify the changes according to the validation requirements and submit your review within 72 hours.

#2671

[USS-Supervisor]

Assignment completed: @Adisaok submitted a validation review on #2671: #2671 (review)

[USS-Supervisor]

@harunsulaiman
You have been assigned to validate this PR #3379 as part of the Chain.Love Validation Bounty Pilot.

Please independently verify the changes according to the validation requirements and submit your review within 72 hours.

#3379

[USS-Supervisor]

@Adisaok
You have been assigned to validate this PR #3067 as part of the Chain.Love Validation Bounty Pilot.

Please independently verify the changes according to the validation requirements and submit your review within 72 hours.

#3067

[USS-Supervisor]

Assignment completed: @Adisaok submitted a validation review on #3067: #3067 (review)

[USS-Supervisor]

Assignment completed: @Adisaok submitted a validation review on #2496: #2496 (review)

[USS-Supervisor]

Assignment completed: @Adisaok submitted a validation review on #2730: #2730 (review)

[USS-Supervisor]

Assignment completed: @Adisaok submitted a validation review on #3489: #3489 (review)

[USS-Supervisor]

Assignment completed: @Adisaok submitted a validation review on #2671: #2671 (review)

[USS-Supervisor]

Assignment completed: @harunsulaiman submitted a validation review on #3127: #3127 (review)

[USS-Supervisor]

@Adisaok
You have been assigned to validate this PR #3476 as part of the Chain.Love Validation Bounty Pilot.

Please independently verify the changes according to the validation requirements and submit your review within 72 hours.

#3476

[USS-Supervisor]

Assignment completed: @Adisaok submitted a validation review on #3476: #3476 (review)

[USS-Supervisor]

@Adisaok
You have been assigned to validate this PR #3106 as part of the Chain.Love Validation Bounty Pilot.

Please independently verify the changes according to the validation requirements and submit your review within 72 hours.

#3106

[USS-Supervisor]

Assignment completed: @Adisaok submitted a validation review on #3476: #3476 (review)