GitTipOpen source runs the world. Now it gets paid.
Every coin launched on GitTip sends its creator fees to a GitHub account, on-chain, from the first trade. The vault that receives them is derived from the GitHub user id, so it is the same on launch day and a year later.
One vault, two journeys
the same vault · address = f(GitHub user id) · computable before it exists
After launch, trading fees accrue inside Pons for the vault. A claim collects them and forwards everything to the wallet the developer chose.
Launching
- Search GitHub. Type a username. GitTip resolves it to the permanent numeric id and shows the avatar.
- See the vault. The vault address is shown before you sign, with a note that the fees will go there.
- Fill in the coin. Name, ticker, description, image (the developer's avatar by default) and an optional dev buy.
- Launch. One transaction creates the vault if needed and launches the coin from it, atomically.
- Done. Fees accrue from the first trade. Nothing more for the launcher to do.
Claiming
- Enter your handle. The claimable balance shows with no wallet and no login.
- Sign in with GitHub. GitTip learns your numeric id only, then forgets the rest. Nothing is stored.
- Connect a wallet. Any wallet. It pays the gas and, by default, receives the funds.
- Claim. The vault verifies the signature, collects any fees still in Pons and pays you. You can claim again any time.
What you have to trust
The contracts have no owner and no upgrade path for vaults. Authority comes from signatures, and the one thing GitTip operates is the service that signs a claim after GitHub confirms who is asking. That is a trust point, and this page keeps it small and visible:
- The signing key is held only in the server's memory, and it signs only for a browser that just proved its GitHub id.
- The list of allowed keys is on-chain, and its owner can cancel a key for every vault in one transaction. Who that owner is, is shown below.
- Every claim is bound to its recipient, a one-time nonce, a ten-minute deadline, the chain and the vault.
- Everything below is read live from the chain, so you can check it without trusting this site.
A compromised signer could authorize a claim to the wrong recipient before it was revoked. Moving to GitHub-login proofs that a vault can verify on-chain (for example with zkEmail) would remove the signer entirely. That is the path to a trustless version.
Questions.
Does the developer really get 100%?
Yes, of the creator fees. When the coin launches, its creator-fee recipient is set to the developer's vault, and the vault has no way to hand that over, so neither the launcher nor GitTip can redirect or take it. GitTip keeps nothing. Pons still charges its own protocol fee on trades; that part never went to a coin's creator. One more thing is outside GitTip's control: Pons's own owner has a protocol-level override for any launch's fee recipient, which only takes effect after a public three-day timelock.
Does the developer need to do anything?
Only to claim. Fees accumulate in their vault whether or not they know about it. To claim they sign in with GitHub, connect any wallet, and send one transaction.
What do I get as the launcher?
You get the coin and whatever you bought with your dev buy. You do not get the creator fees. That is the point.
Why only one wallet approval?
The launch router creates the developer's vault and launches the coin from it in a single transaction, so the coin can never exist without its fees being routed. If anything in the launch fails, all of it is undone and nothing is charged.
Can I launch for an organization?
No. An organization cannot sign in with GitHub the way a person does, so its fees could never be claimed. GitTip refuses organizations to keep fees from getting stuck.
Each developer only gets one coin?
Yes. A vault launches exactly once, so nobody can use an existing vault to launch a second coin against the same developer's reputation.
What if a developer does not want a coin launched for them?
A coin on-chain cannot be unlaunched. A developer can ask us (on X) to hide their vault and refuse new launches for their GitHub account on this site. That is a rule of this site, not of the chain: the contracts themselves are permissionless. The developer keeps every right to claim what is already theirs.
What if the signing key leaks?
A claim needs a signature from a key registered on-chain. If one leaks, the registry's owner removes it for every vault in one transaction, and every vault picks up the new key on its next claim. That only helps while the owner is a different key: the trust panel above shows whether it is. A leaked signature still only pays the recipient it names, once, within ten minutes.
Is GitTip part of GitHub, Robinhood or Pons?
No. GitTip is independent and not affiliated with, endorsed by or sponsored by GitHub, Robinhood or Pons. A coin launched for a developer does not mean they endorse it.