01 / Repository
Start with the code
Pick a public repository with an active GitHub Sponsors recipient.
Launch a coin for a GitHub repository. Launch-only fees go to your wallet; Sponsors payouts are not live.
Creator fee recipient
Sponsors integration · setup in progress
The people behind the code.
How it worksTurn a community’s attention into support for the people building it.
Pick the repository
A public GitHub repo. Any language. Any community.

Verify the Sponsors profile
Linked by the repository. Verified through GitHub.

FROM COMMIT TO COMMUNITY
01 / Repository
Pick a public repository with an active GitHub Sponsors recipient.
02 / Verification
We verify the funding links and the recipient’s public Sponsors profile.
03 / Launch
Choose pump.fun or pons, review the recipient and costs, then sign in your wallet.
Creator fees support the maintainer, not the person launching.
Trades follow the platform’s fee rules.
Automatic collection and attribution are not live. Launch-only fees go to the signing wallet.
GitHub sponsorships require a separate, funded and verified payment flow. This is not active.
Collection, conversion, card credit and sponsorship still require provider integration.
| Memecoin launchpad | One-off donation | gitcash | |
|---|---|---|---|
| What you support | A coin and its community | A creator or project | A public GitHub repository |
| Who gets creator fees | The configured recipient | No trading fees | A verified GitHub Sponsors recipient |
| Recipient verification | Depends on the launch | You check the recipient | GitHub funding links and public Sponsors profiles |
| Where the fees go | Platform-specific | A single donation | Treasury → conversion → one-time sponsorship |
| Launch destinations | Platform-specific | Not a token launch | pump.fun and pons |
| Your wallet | You sign the transaction | You approve the payment | Your keys. Your approval. |
One repository. One recipient.
Repository funding links, recipient identity and payout status. Reviewed together.
Launch appVerify the repository…
A launchpad being built to support open-source projects through GitHub Sponsors. Launch-only mainnet transactions are available with fees going to the signing wallet. Automatic Sponsors payouts are not live.
Public, active repositories that link to a public GitHub Sponsors profile. External donation links alone do not qualify. A Sponsors profile is not approval or endorsement of a token.
No. The Sponsors route uses the recipient listed in the repository’s GitHub funding links, not a custom wallet file.
Collected SOL or Robinhood Chain ETH is converted through Relay to TRON USDT. A confirmed card credit then funds a one-time sponsorship from the configured GitHub billing account. This flow needs connected providers and operator reconciliation.
No. A confirmed bridge transfer, issuer credit, accepted sponsorship and reconciled GitHub payment receipt are separate steps. The maintainer’s bank payout follows GitHub’s own process.
Only the net amount available after launchpad, network, conversion, card and GitHub fees, unless those costs are covered separately. Remainders stay attributed to the repository.
No. Gitcash is experimental, custodial during payout processing, and not independently audited. Tokens can lose all value. GitHub and card-provider approval are required before live payout operation.