Live on GenLayer Testnet Bradbury

Ship the milestone. The grant pays itself.

A funder writes the milestones and sends the whole grant. When the grantee's repository shows the work, anyone names the commit; GenLayer validators read the file at that commit, judge it against the criteria and quote it. Met: the milestone is paid. Not met: it stays open. Missed the deadline: the funder gets it back.

Grant #0 · Tidepool data export2 milestones
CSV export · commit a1b2c3dnot met

The changelog only lists export as planned.

CSV export · commit 9f8e7d6met

“Added the export command: tidepool export --csv writes every station reading to CSV.”

Docsopen

Due in 60 days, or back to the funder.

–Grants
–Milestones met
–Paid (GEN)
–In escrow (GEN)

How it works

The commit decides.

  1. I
    Write

    The funder names the grantee and one public GitHub repository, then 1 to 8 milestones: what it is, the criteria, the file that should show them (a changelog, a docs page), an amount and a deadline. The whole grant is sent.

  2. II
    Build

    The grantee works in the open. Nothing is paid for promises.

  3. III
    Claim

    Anyone names a commit. Validators each fetch that file at that commit, which never changes, and agree on met or not met; for met, on a passage of the file that each of them finds.

  4. IV
    Pay

    Met pays the grantee at once. Not met stays open for a later commit. After its deadline, an open milestone goes back to the funder.

Built for both sides

For funders

  • Pay for delivered work, written down in the repository, not for a report.
  • No review queue: validators read the file against your criteria.
  • Every reading is on record, with the commit and the reason.
  • Missed deadlines come back to you; anyone can send them.

For grantees

  • The whole grant is in escrow before you start.
  • Ship, then claim: payment follows the commit, not a funder's inbox.
  • Not met is not final: fix it and claim again with a new commit.
  • The criteria are fixed when the grant opens; nobody moves the goalposts.
Pinned by the commitThe file is read at a full 40-hex commit from raw.githubusercontent.com: the same bytes for every validator, forever.
Quoted, not guessedMet counts only with a passage from the file that every validator finds in its own copy. Plans, to-dos and “coming soon” are not met.
Honest limitsValidators read what the file says; they do not run the code. Commit dates are set by the author, so criteria should say what the file must show, not when.

Grants

Every grant, read live from the contract.

Reading the contract…

Open a grant

Milestones (1 to 8; leave a title empty to skip it). You send the total now.

FAQ

Who decides that a milestone is met?

GenLayer validators. Each one fetches the named file at the named commit and answers: does it show every criterion, specifically, as done? A result counts only when they agree, and met also needs a passage of the file that every validator finds.

Why a commit and not the main branch?

A branch moves; a commit never changes. Reading the file at a full commit SHA pins the evidence: every validator, today or later, sees the same bytes.

What if the file is missing at that commit?

The claim reverts and nothing changes. Name a commit that has the file.

Can a claim be repeated?

A milestone that is not met stays open: anyone can claim it again with another commit until its deadline. A met milestone is paid once.

Does it run the code?

No. It judges what the file says against the criteria. Write criteria that a changelog, a release note or a docs page can show.

Fund work, not promises.

Write the milestones, escrow the grant, and let consensus read the commits.

Open a grant