How it works

#Overview

A gitpad market moves through four stages:

1. Repository. A public GitHub repository is resolved to its permanent numeric ID.
2. Market. Someone launches the repository's canonical token market on a Meteora Dynamic Bonding Curve.
3. Trading and graduation. Trades pay fees. When the curve holds 85 SOL of real reserve, the market migrates to Meteora DAMM v2.
4. Builder paid. A current GitHub admin of the repository verifies, binds a payout wallet and claims the accrued fees in SOL.

Public GitHub repo
  -> canonical market on Meteora DBC
  -> trades pay builder fees (accrue even before builders join)
  -> curve reaches 85 SOL real reserve -> verified migration to DAMM v2
  -> current GitHub admin verifies, binds wallet, claims SOL

#1. Repository

Paste a public GitHub repository URL on the home page or at /launch, or pick a candidate from /find-repos. gitpad asks GitHub for the repository and records its numeric ID. That ID, not the name, is the market's identity.

If the repository already has a market, gitpad opens it instead of offering a new launch. Private and archived repositories are not eligible. See Repository identity.

#2. Market

The launcher reviews the repository, chooses a token name, ticker and artwork, optionally adds an initial buy of up to 3% of supply, and reviews the simulated cost. They then approve one transaction in their own Solana wallet. That transaction creates the token mint and its canonical DBC pool, and executes the optional first buy.

Every token has a fixed supply of 1,000,000,000. gitpad indexes the launch once it is finalized on Solana, and the market appears in /explore. See Launching.

#3. Trading and graduation

Traders buy and sell against the bonding curve. Each fee-paying trade on the curve pays a 1.75% fee:

Buys add SOL to the curve's reserve; sells remove it. When the real SOL reserve reaches the market's target (85 SOL for current launches), Meteora migrates the market to a DAMM v2 pool. The migrated liquidity is split into two permanently locked positions. After migration is verified, gitpad trades the same token in that pool. See Trading and Graduation.

The wallet that launched the market earns a discovery reward: half of gitpad's share of curve fees, until graduation, 30 days, or 2.5 SOL earned, whichever comes first. This does not change the builders' share. See Discovery rewards.

#4. Builder paid

Builder fees accrue from the first trade, whether or not anyone connected to the repository has signed up. To claim:

1. A user connects GitHub through the gitpad GitHub App.
2. gitpad checks, with GitHub, that this user currently has admin permission on the repository.
3. The admin signs a message with the payout wallet to bind it to the repository.
4. The admin reviews the available amount and claims. gitpad's protected signer sends the fees directly to the bound wallet.

Claims work before and after graduation. After graduation, builder fees come from the locked creator position in the DAMM v2 pool. See Builders and Fees.

#What gitpad verifies

• GitHub is the source of truth for repository identity and current admin permission.
• Solana and Meteora are the source of truth for pools, finalized trades, earned fees, migration and settlement.
• gitpad's database records workflow state and balances derived from that evidence. Payout receipts are checked against finalized transactions before they are shown as paid.

Receipts and aggregate figures are public on /stats. See Stats and receipts.