Docs

How it works

1. Fork a repo

Anyone launches a coin for a public, non-fork repo. The Forkpad service checks the repo on GitHub and signs a short-lived launch voucher; the program verifies it on chain. One live coin per repo.

2. Fees split where the road forks

Every creator fee collected from pump.fun or PumpSwap is split by the program: 50% maintainer pool, 40% bounty pool, 5% to the launcher, 5% buys and burns $FORKPAD. Nothing goes to a treasury.

3. Merged PRs get paid

When a PR is merged into the repo's default branch, the service records it on chain and it takes 10% of the bounty pool (at most 5 SOL) as a slice. After a 24 h review window, the PR author claims it with the wallet bound to their GitHub login.

4. The maintainer claims the mailbox

The repo owner (or an org admin) signs in with GitHub, binds a wallet, waits the 24 h safety window, and claims the maintainer pool. Later fees keep landing there. A maintainer can also opt the repo out: its pools then buy and burn the coin.

Parameters

Launch fee

0.02 SOL

Fee split

maintainer 50%, PR bounty 40%, launcher 5%, $FORKPAD buy and burn 5%

Per merged PR

10% of the bounty pool, at most 5 SOL; below 0.005 SOL it pays nothing

PRs per repo per day

at most 20

Eligible PR

merged into the default branch after the coin launched and within 24 h of being picked up; author is not a bot, not the merger and not the maintainer; account at least 90 days old; at most 3 paid PRs per author per repo per 7 days

Review window

24 h before a slice can be claimed

Unclaimed slice

returns to the bounty pool after 180 days

Wallet binding delay

24 h for GitHub logins and maintainers

Smallest top-up

0.01 SOL, all of it to the bounty pool

Parameter changes

announced on chain, effective after 24 h

Trust points

The Forkpad service attests who is who on GitHub: which repo may launch, who maintains it, who owns a login, which PR merged when. It cannot choose amounts: those come from the on-chain pools and rules.

Every payout from an attestation waits a window (24 h for slices and bindings) during which a separate guardian key watches GitHub and can veto a wrong slice or cancel a wrong binding. A vetoed slice goes back to the bounty pool. The guardian can only send SOL back into the repo's own pool.

The admin has no path to any repo, slice, coin or login account. Unclaimed money never goes to the launcher, the pad or a treasury.

Known limits: a repo admin with aged extra GitHub accounts could merge his own PRs; the 10% per PR, the per-author cap, the daily cap and the public PR links bound it. Eligibility filters (account age, bots, per-author cap) are service policy, not chain rules.