Docs

How GitPad works

GitPad is a fee bridge. A token points its creator fees at us, we claim them on chain, and % is paid to a GitHub developer through GitHub Sponsors. Nobody has to sign up to be paid.

CONTENTS
    1

    Overview

    GitPad turns a token's creator fees into dollars for the people who write open source. A deployer launches a token on a supported venue and points its creator fees at the GitPad treasury. The token's description names a GitHub account, and that account is who the fees are for.

    Everything between the two is mechanical. Fees accrue to the treasury as the token trades, GitPad claims them on chain, % is converted to dollars and paid to the developer through GitHub Sponsors, and % buys and burns it. Every step is recorded against the claim that produced it, and every payout is confirmed in public.

    The developer is not asked to do anything first. There is no account to make and no wallet to connect, so a payout can arrive from a token they have never heard of. Control sits where it already did: GitHub decides who can receive sponsorships, and a developer can ask us to stop at any time. Section 13 covers stopping payments.

    1
    A token directs its feesThe deployer points 100% of creator fees at the GitPad treasury, permanently. See section 3.
    2
    The description names a handleOne line in the token description says who the fees belong to. See section 4.
    3
    GitPad claims and splitsClaims run on a schedule and split /. See sections 5 and 6.
    4
    The developer is paidDollars arrive as a one-time GitHub sponsorship. See section 7.
    2

    Supported venues

    VenueChainFees paid inHow we detect
    Pons v2Robinhood ChainETHCreator fee recipient set to the treasury at deploy
    pump.funSolanaSOLComing later

    Other venues are added when their creator fees can be pointed at a third party on chain and locked there.

    3

    Directing fees

    When a token is deployed through GitPad on Pons, the GitPad treasury on Robinhood Chain is set as the token's creator fee recipient. The Launch page does this in the same transaction that creates the token, so there is no window where the fees point anywhere else.

    Tokens already launched on Pons can be registered from the Launch page if their creator wallet moves the fee recipient to the treasury.

    4

    Naming the recipient

    The Launch page adds one line to the token description: Fees → github.com/<handle> via @GitPad. That line is the only thing GitPad reads to decide who is paid. It can name a user or an organisation.

    The handle is resolved to GitHub's numeric account id at the first claim. If the account is later renamed, payouts follow the id, not the old name. If the line is missing or the account does not exist, the fees are held; see section 14.

    5

    The / split

    Every claim splits at the moment it lands: % belongs to the developer, % belongs to the protocol. An optional deployer reward of up to 10% comes out of the developer's share and is paid to the deployer wallet on the same schedule.

    The protocol share pays for execution first: claim transactions, bridging, conversion spread and payout fees. What is left buys on the open market and burns it.

    6

    How claims work

    Creator fees accrue in ETH in the Pons fee vault of each token. GitPad claims them to the Robinhood Chain treasury on a schedule, in batches of tokens per transaction. Vaults holding less than the gas a claim would cost are skipped until they grow.

    Each claim is recorded against the token it came from, so every dollar paid later can be traced back to the claim that produced it.

    7

    Getting your fees

    If you are the developer named on a token, you do not need to do anything. When your share is converted, it is sent to your GitHub account as a one-time sponsorship from the GitPad organisation. GitHub then pays it out to your bank the way it pays every other sponsorship.

    Signing in with GitHub to receive your share in ETH to a wallet instead is coming soon.

    8

    GitHub Sponsors setup

    To receive sponsorships, a GitHub account needs a GitHub Sponsors profile with payouts enabled. It takes a few minutes at github.com/sponsors and is available in every region GitHub Sponsors supports. Until it is set up, your share is held as owed.

    9

    Unclaimed payments

    Owed amounts are kept in dollars and shown next to each token on the Payments page. They do not expire. Once a Sponsors profile is enabled, everything owed is paid in the next payout run.

    10

    The public confirmation

    Every payout is listed on the Payments page with the claim that funded it, the conversion it was part of and the time it was sent. Expand any row to see the on-chain claim transaction and the payout reference.

    11

    The treasury and cross-chain

    All creator fees land in the GitPad treasury on Robinhood Chain. The developer share is bridged to Ethereum mainnet and deposited to Kraken as ETH, so every conversion runs from one account. The protocol share never leaves Robinhood Chain. The Capital Flow page shows each stage.

    12

    and the buyback

    is the protocol token, launched on Pons on Robinhood Chain. After execution costs, the protocol share buys on its Pons market in ETH and sends it to the 0x000000000000000000000000000000000000dEaD address, where it can never move again. Every buy and burn is listed on the Analytics page with its transaction.

    Contract address:

    13

    Stopping payments

    Any developer can stop payments to their account. Contact GitPad from the GitHub account itself, or from its linked X account, and ask to opt out. From then on the developer share of every token naming you is burned with the protocol share instead of being paid. A one-click opt-out after signing in with GitHub is coming soon.

    14

    If a token is not registering

    • The fee line is missing from the description, or names an account that does not exist.
    • The token was launched outside GitPad and its creator fees still point at the creator wallet.
    • The fee vault is still under the claim threshold in section 6.

    Fees from tokens that cannot be matched are held for review, not paid to anyone else.

    15

    Glossary

    Creator feeThe share of trading fees a venue pays to a token's creator.
    TreasuryThe GitPad wallets creator fees are pointed at.
    OwedA developer's share that is waiting for a Sponsors profile.
    Off-rampConverting claimed crypto into dollars.
    Buyback and burnBuying with the protocol share and destroying it.
    ·

    Terms of Use

    GitPad is software that routes creator fees. Launching a token is your own action, signed by your own wallet, and on-chain transactions are final. Tokens launched through GitPad are not endorsed by, affiliated with or created by the developers they name unless those developers say so themselves. Do not use a developer's name to imply an endorsement they have not given.

    ·

    Privacy

    GitPad reads public on-chain data and public GitHub profiles. It does not ask for or store any personal data.

    ·

    Disclosures

    Memecoins are highly speculative and can lose all of their value. Nothing on GitPad is investment advice. GitPad is not affiliated with GitHub, Inc., pump.fun, Pons or Kraken.