github is the source. gitpad gives it a market.
any public github repository — github.com/owner/repo or just owner/repo.
gitpad pulls stars, forks, contributors and commits straight from github.
configure it and launch on the pons bonding curve in under a minute.
trade the market and watch the repository ship, release and grow.
from a repository url to a live, tradeable market — and where the fees land.
any public github repository works — github.com/owner/repo, a deep link to an issue or pull request, or just owner/repo. gitpad parses it, rejects reserved paths, and resolves the canonical owner and repo name through the github api.
gitpad pulls live metadata straight from github's public rest api — stars, forks, contributors, recent commits, the latest release and language breakdown. nothing is fabricated. if github is rate-limited or down, gitpad shows an honest 'unavailable' state instead of inventing numbers.
configure an optional logo and description, then launch through the pons v2 bonding-curve factory on robinhood chain. the repository snapshot — owner, name, description, stars and avatar — is stored onchain in the launch record so the market stays anchored to the code it represents.
trade the market and watch the repository ship. the market page keeps showing real commits, releases and contributors as the project evolves — the onchain market and the open-source work stay linked.
gitpad routes creator fees to a single payout wallet and lets verified repo admins claim them through github. the person who launches the coin never receives fees.
every coin's creator fees route to the gitpad payout wallet — never to the deployer who launched it. the deployer earns nothing from fees; only the verified repository admin does.
each coin page has a 'claim fees with github' button. the admin signs in through github oauth (callback host gitpad.cc). gitpad checks their github identity against the repository's collaborators and owners — only admins pass. once verified, they choose which wallet receives the payout.
a verified claim is written to the fee_claims table: the coin, the verified github login, the repo, and the chosen payout wallet. this is the source of truth for who earned what.
payouts are manual for now. gitpad records who is verified and their wallet, but does not yet send the money. you fund the payout wallet and pay verified admins from it. automatic sending is the next step and needs the wallet's key secured plus a per-coin fee ledger.
note: new launches are paused until the gitpad payout wallet address is set. every coin's fees depend on it. once configured, verified admins can claim from each coin page.
any public github repository. gitpad verifies it exists through github's api before a launch is possible.
anyone with a connected wallet. launching costs a small fee on pons.
no. fees go to the gitpad payout wallet and are claimed only by the verified repository admin — never the deployer.
no. gitpad markets are community-created and are not necessarily affiliated with the referenced repository or its maintainers. a disclaimer is shown on every market page.
yes. stars, forks, contributors, commits and releases come live from github's public api. if github is unavailable, gitpad says so instead of guessing.
yes. launches go through the pons v2 factory on robinhood chain and graduate into locked uniswap v4 liquidity.
github allows roughly 60 unauthenticated lookups per hour per visitor. once exceeded, gitpad shows 'unavailable' rather than stale or invented data.