Legal

Not legal advice. Have counsel review before mainnet, public token solicitation, or marketing in your jurisdictions. This page is the product-kit checklist for GitFuel.

1. Nature of the product

GitFuel is software that helps users launch and trade Solana tokens associated with public GitHub repositories via pump.fun / PumpSwap. Tokens may be extremely volatile, illiquid, or worthless. Nothing in the app is financial, investment, or legal advice.

2. No affiliation

GitFuel is not affiliated with, endorsed by, or sponsored by:

  • GitHub, Inc. / Microsoft
  • pump.fun / PumpSwap operators
  • Solana Foundation
  • repo.ing / REPOING or related entities

GitHub® and other marks belong to their owners. Use of public GitHub APIs and public repo metadata is under GitHub Terms; this app does not imply an official partnership.

3. Trademarks and brand

GitFuel is an original brand and is not repo.ing / REPOING. It does not copy those logos, mascots, diagram artwork, or trademarked phrases. Factual comparison belongs in docs, not in the wordmark.

4. Tokens and securities risk

Launching or promoting tokens can implicate securities, commodities, and money-transmission rules depending on jurisdiction and how $GITFUEL or repo coins are marketed. Avoid promises of profit, guaranteed buybacks, or passive income. Proposed revenue and buyback policies stay labeled proposed until executed under a reviewed policy. This interface does not fabricate transactions.

5. Creator fees and claims

Fee routing to a verified GitHub owner or admin depends on OAuth and GitHub permission data that can change: admin removed, repo transferred, org policy changed. A claim is proof of control at verification time, not a legal ownership finding. Contested claims, stolen accounts, and org disputes need a published process — freeze, dual-control, support — before anyone promises irrevocable payouts. Phase 1 does not run that dispute process. Escrow and fee-sharing configs should be described as they are: until a verified claim, the builder slice may sit on a platform treasury pubkey, and the launcher who created the sharing config remains the admin who can change shares.

6. User content and IP

Repo names, descriptions, and avatars are third-party content. Launching a coin does not grant IP rights in the software. The app blocks private repos. Do not impersonate projects with deceptive metadata, and do not violate GitHub or pump.fun terms. Abuse and takedown contacts should be published before a public launch. This build does not invent an inbox.

7. Sanctions, geo, AML

Consider geoblocking or soft warnings where required. Phase 1 is designed around user-signed transactions and does not take custody of trade proceeds. A hot wallet or custodial crank, if one is added later, is high-risk and needs audits, key management, and disclosures. The labeled treasury address used for an interim fee share is not a promise of custody quality.

8. Privacy

OAuth tokens are stored in an encrypted session cookie with the GitHub user id and login, and only so the permission check can run. Declare retention before production and encrypt at rest if the token moves to a database. A privacy policy should cover GitHub profile data, wallet addresses, IP logs, and analytics. Public markets can expose a link between a GitHub identity and a Solana wallet once a builder claims. The claim screen says that before you bind.

9. Open source and third-party licenses

Respect the licenses of @pump-fun/pump-sdk, wallet-adapter, and the other dependencies. If GitFuel itself is open-sourced, pick an SPDX license and a CONTRIBUTING guide first.

10. Disclaimer

GitFuel is experimental software. Tokens can lose all value. Not affiliated with GitHub or pump.fun. No investment advice. Creator fee claims require GitHub admin verification and are not guarantees of payment. Revenue and buyback figures are proposed policies unless linked to verified on-chain transactions.

11. Before public launch

  • Counsel review (token, consumer, terms, privacy)
  • Terms of service, privacy policy, cookie notice
  • Abuse, DMCA, and impersonation contacts
  • Multisig for treasury; avoid a single-EOA policy fund
  • Fee-sharing docs that match the on-chain config
  • No placeholder “executed buyback” UI — this build does not have one
  • Trademark search for GitFuel / GITFUEL in the markets you enter