MergeProof

Economics

The Money Math

Every number in the protocol is derived from first principles. Drag the sliders, simulate scenarios, and see why collusion always costs more than honesty.

Section 01

Build a Bounty

Drag the sliders and watch every derived value recalculate in real-time. The CLI command updates live below.

Bounty Amount$10,000
Stake Ratio10%
Review Window72h
Attestation Pool5%
terminal
$ mergeproof bounty create \ --repo owner/repo \ --issue 42 \ --amount 10000 \ --stake-ratio 10 \ --window 72 \ --attestation-pool 5

Owner

Total Deposit$10,500
Bounty$10,000
Attestation Pool$500
Review Window72h

Submitter

Stake Required$1,000
Stake Ratio10%
Max Attempts3

Hunters

Bug Report Cost$25
Attestation Cost$100
Max Attestors10

Section 02

Simulate a Review

Step through a review window. File bugs, add attestations, advance time, then close the window to see the outcome.

Attempt:1 of 3
0h / 72h
0h24h48h (attest opens)72h
Bounty: $10,000Bugs: 0Attestations: 0Status: IN REVIEW

Event Log

[00:00]PR submitted by developer. Commit abc123 locked.

Section 03

Why Gaming Loses

The 10% protocol fee on bug payouts makes collusion strictly dominated. Honest play is always more profitable.

Scenario: Plant 10 minor bugs with an accomplice

HONEST PATH

Submitter claims$10,000 (bounty)
Stake returned$1,000
Total payout$11,000

COLLUSION ATTEMPT

Bounty after 10 minor bugs$9,000 (10% reduction)
Submitter claims$9,000 + $1,000 stake
Accomplice bug rewards$1,000 gross → $900 net
Combined total$10,900
-$100vs honest path. Protocol fees eat the scheme.

Scenario: Collude to drain bounty to floor

HONEST PATH

Submitter claims$10,000 (bounty)
Stake returned$1,000
Total payout$11,000

COLLUSION AT FLOOR

Floor hit → auto-rejectPR rejected
Submitter bounty$0 (rejected, no claim)
Submitter stake-$1,000 (forfeited)
Accomplice bug rewards$5,000 × 90% = $4,500
Combined total$3,500
-$7,500vs honest path. Collusion at floor is catastrophic.

Key insight: Bug rewards come directly from bounty reduction. Whatever the accomplice earns, the submitter loses — minus protocol fees. Every collusion path results in less total value than honest play.

Section 04

Deposits In, Payouts Out

Watch deposits flow to payouts. Change the bounty or scenario and every number recalculates. Totals always match — zero-sum.

Bounty Amount$2,000

Scenario

Deposits (in)

Owner (bounty)$2,000
Owner (attest pool)$100
Submitter (stake)$200
2x Hunters (bug stakes)$10
Total In$2,310

Payouts (out)

Submitter (reduced bounty)$1,740
Submitter (stake back)$200
Hunters (bug net)$234
Hunters (stakes back)$10
Owner (unused pool)$100
Treasury (fees)$26
Total Out$2,310

Deposits = Payouts — Zero-sum verified

Live on GenLayer

The math works. Try it yourself.

Browse open bounties, stake on your code, and see the economics in action.