Nobody pays for the code everyone runs on. Trading fees can.
Launch a coin for any GitHub repository. Every trade pays a 1% fee, and 80% of it routes to a vault belonging to that repository — which the maintainer can claim whenever they turn up. They hold no tokens and sign up for nothing.
The maintainer is not asked, notified or required to approve anything. That is deliberate, and the argument for it — plus the cost — is set out below.
Where the money actually goes
The fee already exists. Every launchpad takes one. The only thing GitSend changes is who ends up holding it.
The split is a contract parameter, capped at 10% total fee by MAX_FEE_BPS — the owner cannot quietly raise it past that ceiling.
Someone picks a repository
Any repository. The coin launches on a bonding curve and trades like any other coin on the chain.
The vault is keyed to GitHub's numeric id
Not the username. Usernames get abandoned and re-registered; numeric ids are permanent. A maintainer can rename their account or move the repo and the money stays pointed at them.
Fees accumulate whether or not anyone shows up
The vault fills from the first trade. No one has to claim it, watch it, or know it exists for it to keep filling.
The maintainer proves the account and takes it
Sign in with GitHub, get a signed claim, withdraw to any wallet — or take it in dollars through GitHub Sponsors.
What 0.8% is actually worth
Drag it. This is multiplication, not a forecast — a coin nobody trades pays nobody, and most coins are not traded.
Why this is not the usual number
Most launchpads pay the coin's creator a sliver of the fee — on pump.fun it is 0.05%. Here the creator share is 0.8%, sixteen times that, and it is pointed at the repository rather than at whoever clicked launch.
And the catch
Volume is the entire story. At $2,000 a day this is coffee money. The floor is not that it pays well — it is that the money accrues with nobody doing anything, and it is waiting whenever the maintainer decides to look.
You hold nothing, so you can lose nothing
Zero tokens, ever
No allocation, no vesting, no treasury share. You receive the fee, never the coin — so there is nothing for you to sell and nobody can accuse you of dumping on your own users.
Claim in dollars or on-chain
Verify the GitHub account, then withdraw to any address, or route it through GitHub Sponsors as ordinary fiat income.
What it does cost you
Reputational exposure. A coin carrying your project's name that collapses is not neutral for the project, even though you never touched it. That is a real cost and we are not going to pretend otherwise.
Coins
Example rows, marked as such. Real ones appear here once the launchpad is live.
| Repository | Coin | Vault balance | Status |
|---|
Parameters, as written in the code
These are the deploy-script defaults in GitSendLaunchpad, not marketing rounding.
Where this actually is
Coins launch without the maintainer's permission
That is accurate and we are not going to soften it. Requiring opt-in first recreates the exact problem this exists to solve — it asks a maintainer to trust a crypto product before a single dollar exists. Money accruing first, conversation second, is the whole design.
The cost of that choice is the row above it: there is no opt-out yet. If you maintain something and you want out, say so and we would rather hear it from you.