LIVE ON GENLAYER BRADBURY

Evidence-settled
builder bounties.

Evidence-settled builder bounty protocol on GenLayer. Sponsors fund outcomes, wallet-bound public proofs establish account control, and validator consensus adjudicates evidence quality.

01Sponsor locks reward
02Builder submits evidence
03Score gates eligibility
04Challenge can reduce / deny
05Qualified builder claims

V10 verifies wallet control of a public challenge resource—not legal identity—and records validator-consensus quality judgements rather than claiming objective universal quality.

VERIFIED EVIDENCE · V10

Public control + quality adjudication

V10 proves a wallet controlled a public HTTPS resource containing its one-time challenge. Validators then assess product evidence against a rubric. It does not claim legal identity or objective universal quality.

01 Sponsor verified campaign
02 Submit verifiable evidence
LIVE CONTRACT TELEMETRY

Protocol overview

Latest accepted state Finalization may be pending

Accepted / finalization pending: live reads use the latest accepted contract state. A scheduled claim is not described as paid until finality is known.

OPEN SETTLEMENTS

Builder campaigns

Reading accepted contract state…
SPONSOR A SETTLEMENT

Create and fund a campaign

The deposited GEN becomes the campaign reward pool. Every accepted score at or above your threshold unlocks one fixed claim, while creator counter-evidence can revise eligibility before claim.

Payable value is sent in wei. The transaction hash is immediate; campaign state appears only after accepted execution succeeds.
DEPLOYMENT RECORD

Deployment proof

✓ ON-CHAIN PROOF

Transaction references are fixed deployment artifacts. Explorer status is the source of truth for finality.

ProofScore v9 · GenLayer BradburyAccepted is not finalized. Payout transfers execute on finalization.Explorer ↗