Mergit — Merge it. Get paid.

01 · The problem

Paying builders is still a manual process.

Every ecosystem knows it needs developers. Almost none can pay them for shipped work without friction, and a new chain lives or dies by the builders it attracts.

Slow

Weeks to months

Grant rounds, review queues, multisig sign-offs. The work ships today and the payment arrives next quarter.

Manual

Committees decide

People read applications, not code. Review is subjective and does not scale with the ecosystem.

Farmable

Sybils drain the pool

Identity filters fail. Fake accounts and recycled repositories capture funds meant for real builders.

PrecedentWhat it provedThe bottleneck

Optimism Retro Funding100M+ OP paid to builders for work already shipped.Badgeholders review by hand, round by round.

Gitcoin and grant programsTens of millions distributed. Builders show up when the money is real.Applications, committees, and chronic sybil farming.

02 · The real run

The merge is the invoice.

Lock a bounty on-chain. When the pull request is merged and its tests pass, the agent verifies it from GitHub and the escrow pays the developer. Nobody signs off. Nobody chases a payment.

What you see here is not a mockup. It is the replay of what happened to mergit-demo#2 on 19 September 2026, with the amounts, hashes and transaction read from GIWA Sepolia.

20 sfrom merge to payment

98.5%of the bounty goes to the developer

0committees, forms or invoices

The pull request ↗ The settlement ↗

mergit · pay-on-merge · odiseo159-beep/mergit-demoreplay

00.0s

since the merge
PR #2 · Sep 19, 2026 · UTC

Real events, replayed in real time

03 · How it works

Judgement off-chain. Custody on-chain.

The agent lives inside GitHub Actions and decides. The money never touches it: it waits in the contract until the two conditions hold.

Lock

A protocol posts a bounty and the reward is locked in the contract on GIWA. Nobody can move it, Mergit included.

Build

A developer ships the work the normal way: a pull request, reviewed and merged by the maintainers.

Verify

Every merge wakes the agent. It reads the pull request through the GitHub API and hashes exactly what it saw.

Pay

If both conditions hold, the escrow pays the author's registered wallet and records the evidence hash on-chain.

What counts as verified · five rules, written in code

The pull request is merged. Unmerged work is not delivered work, and a maintainer accepted it, not the author.
CI is read on the head commit, where the tests for the submitted work ran. The merge commit goes into the evidence.
No CI means no payment. Missing checks are not passing checks. A verifier that approves missing evidence is a rubber stamp.
Neutral and skipped do not block. They mean "does not apply", not "failed".
Both CI systems are read: modern check runs and legacy statuses, because repositories use one, the other, or both.

04 · Why GIWA

A new chain lives or dies by the builders it attracts.

Ecosystem

Built with Optimism

GIWA is an Ethereum L2 on the OP Stack, in partnership with the Optimism Foundation, the ecosystem that pioneered retroactive builder funding. Mergit brings that idea to GIWA, automated.

Timing

Builders are the scarce resource

Mergit turns funding into shipped code that lands on GIWA, instead of into applications. Low OP Stack fees make even small bounties viable.

Synergy

Its own rewards, settled by Mergit

GIWA already invests in builders, manually. Route part of that through Mergit and every payout becomes on-chain activity from a real builder, on GIWA.

05 · Roadmap

From paying for a merge to knowing who really builds.

Each step is a commit on the same branch. The red one is where the project stands today.

Now · live on testnet

The merge pays on its own

MergitEscrow deployed and source-verified on GIWA Sepolia.
Agent v1: merged plus CI green on the head commit, evidence hashed into the payment.
The agent runs inside GitHub Actions on every merge, and comments the receipt on the pull request.
Developers claim their GitHub login on-chain, with a proof the agent re-checks before it pays.
A second escrow adds an opt-in challenge window, per bounty, deployed and verified.
A bounty can be funded, and a login claimed, from the browser, and every builder has a public record.

Next · the protocol

One click, and fewer things to trust

A GitHub App any repository can install, instead of a workflow file.
Repositories that are not ours, funded by protocols that are not us.
Bounty conformance: a report on the pull request saying what the bounty asked for, what the diff changed, and what no test covers. It informs the maintainer before the merge. It never triggers or blocks a payment.
Independent verifiers, a bounty board, stablecoin payouts, mainnet.

Then · builder reputation

A record of work that cannot be farmed

Every settlement becomes a verified record of real, merged, tested work.
Builder profiles and a GIWA leaderboard, ranked by work that was actually paid. The first cut is live at /p, and it sets aside anything a wallet funded for itself.
Ecosystem rewards without applications.

Exploring · subject to regulation

Repo funding pools

A project's revenue routed into its own repository's bounty pool, so money follows merged work instead of attention.

MergitEscrow · 0xffcf…5879, verified on GIWA Sepolia ↗ · 14 tests · solc 0.8.24 · no owner, no pause, no upgrade.