Builders

#Who can claim

Builder fees for a repository can be claimed by a GitHub user who currently has admin permission on it. Write, maintain or triage permission is not enough.

You do not need to have launched the market, and you do not need to hold its token. Fees accrue from the first trade, whether or not you have signed up.

#What you need

• A GitHub account with current admin permission on the repository.
• A Solana wallet to receive payouts. You sign one message with it; you do not send SOL to claim builder fees.

#Claim in four steps

Start from the market's claim page or from /builders.

#1. Connect GitHub

Connect GitHub through the gitpad GitHub App. If asked, install the App or grant it access to the repository. For a repository owned by an organization, an organization administrator may need to approve that access.

The App requests one repository permission: Metadata: read. It does not request code access, write access or repository administration permission. GitHub's authorization screen says the App acts on your behalf because gitpad needs to identify you and check your permission.

#2. Verify admin access

gitpad asks GitHub for your current, effective permission on the repository, identified by its numeric ID. Only an admin result is accepted. The check accounts for access granted through teams, organizations and enterprises.

Your GitHub session is kept for at most one hour, encrypted in a secure, HttpOnly cookie. gitpad checks GitHub again before each sensitive action; a past login is never enough.

#3. Bind a payout wallet

Connect the wallet that should receive payouts and sign the binding message. It looks like this:

gitpad repository beneficiary v1
I bind this Solana wallet as beneficiary for the repository.
Chain: Solana
Repository ID: <numeric repository ID>
Wallet: <your Solana address>
Nonce: <one-time random value>
Expires: <UTC timestamp>

Signing this message proves you control the wallet. It does not send a transaction or spend SOL. Each message can be used once and expires after five minutes. Each repository has one active payout wallet.

#4. Review and claim

Review the available amount and the saved payout wallet, then select Claim. The review is bound to your session, the repository, the wallet, the exact amount and the total already paid, and it expires after ten minutes.

gitpad then checks your GitHub permission again, confirms the on-chain fee balance matches its ledger, and its protected creator signer sends the fees directly from the pool to your bound wallet. You do not sign a transfer. The claim is shown as paid only after gitpad verifies the finalized transaction and the amount your wallet received.

#Earnings labels

Claiming lowers the available balance and raises the paid total. Lifetime earned does not change. Trades that land during a claim stay in the pool for your next claim.

#Multiple repositories

/builders lists tokenized public repositories where your GitHub account currently has admin access, with totals for available, lifetime earned and paid.

• Set wallet binds one wallet to up to 100 repositories that do not yet have a payout wallet, with a single signed message listing every repository ID. Existing payout wallets are never overwritten this way; change them individually from the repository's claim page.
• Claim all ready fees submits a separate claim for each ready repository and shows a receipt or issue for each one. Keep the page open while the queue runs. A failure on one repository does not undo payouts that already completed.

#When admins change

Permission is checked with GitHub each time, so the current admins are always the ones who can act:

• A new admin can verify and claim. A current admin can change the payout wallet from the repository's claim page.
• Someone who loses admin access can no longer bind a wallet or claim, even if they did before.
• Binding a wallet alone does not authorize a payout. Every claim rechecks current permission.
• Payouts already settled are final. They are not reversed or paid again after an ownership or wallet change.

#Builder token allocation

Markets enrolled in the builder allocation reserve 1% of supply (10,000,000 tokens) for the repository's builders. The allocation:

• is reserved at launch from the fixed supply, with no extra minting;
• becomes claimable only after the market's verified graduation;
• is paid once per market to the payout wallet bound by a current admin;
• cannot be claimed again after a wallet or ownership change once it has been paid.

The market page shows whether the market is enrolled and the allocation's state. Builder SOL fees are separate and can be claimed before graduation.

#After graduation

Claims continue after graduation. Fees then come from the permanently locked creator position in the DAMM v2 pool, and a single claim can include both remaining curve fees and DAMM fees. Because the DAMM claim withdraws all accrued position fees, the review notes that fees earned just before confirmation can be included. See Graduation.

#Earnings reminders

When email delivery is configured, signed-in builders with a payout wallet can turn on Earnings reminders from /builders. You confirm your address through an email link. Reminders are sent at most once a day, only when at least 0.05 SOL is available and at least 0.05 SOL of new earnings has been verified since the last reminder. The email links to the normal claim flow and cannot authorize a payout.

#Show your earnings

Add the builder fees badge to your README so contributors and users can see what the repository has earned. See README badge.

#Common issues