Terms of Service

By signing in, linking a GitHub repository, linking a Solana wallet, or trading a token launched on GitShipt, you accept these Terms. If you do not agree, do not use the service.

GitShipt is provided strictly on an “as is” and “as available” basis with no warranty of any kind. These Terms apply to the website at gitshipt.com, all subdomains, and any associated APIs or webhooks operated by the GitShipt team.

GitShipt lets a GitHub repository owner mint a token whose metadata, branding, and royalty splits are bound to that repository. Tokens are launched through the Bags.fm SDK on the Solana network.

When the token trades, a configured share of the swap fees is claimed by GitShipt on behalf of the project and redistributed to the repository's top contributors, ranked by an automated scoring workflow that runs on a daily cadence. Payouts settle directly to each contributor's linked Solana wallet.

You must be at least the age of legal majority in your jurisdiction and have a valid GitHub account in good standing to use GitShipt. You must not be located in, a resident of, or accessing the service from any country or region subject to comprehensive U.S. sanctions, and you must not be a person designated on any U.S. or applicable international sanctions list.

You are responsible for compliance with all laws that apply to you, including local regulations on token issuance, trading, and tax reporting.

By initiating a launch you authorize GitShipt to mint a Bags.fm token bound to the GitHub repository you select and to register the resulting royalty split with the repository's top contributors as recipients. You retain full ownership of your repository, its source code, and its license. GitShipt takes no equity in your project and acquires no rights to your code.

You represent that you have the authority to launch a token representing the repository in question and that the repository's contents do not violate any third party's rights. You are solely responsible for the repository, its branding, and any communications you make about the token.

GitShipt does not custody user funds. Trades occur on-chain through Bags.fm liquidity. Fee claims are executed by an automated workflow that pulls accrued fees into a short-lived hot escrow wallet and immediately distributes them to contributor wallets in the same workflow run.

The escrow window is the only period during which GitShipt technically holds funds, and it exists solely to batch a single on-chain transaction. We do not promise any specific payout amount, frequency beyond “daily best effort,” or transaction inclusion latency. On-chain failures, congestion, or RPC outages may delay distributions.

You agree not to:

• launch tokens for repositories you do not own or have permission to represent;
• impersonate another project, person, or organization, including by reusing names, logos, or branding;
• manipulate trading volume, wash trade, or otherwise inflate fee accrual to redirect payouts;
• spam the platform with low-effort or duplicate launches;
• use the service to facilitate illegal activity, fraud, or evasion of sanctions; or
• attempt to bypass authentication, rate limiting, the kill switch, or any other security control.

GitShipt reserves the right, at its sole discretion, to pause or permanently kill any project, suspend any account, freeze pending payouts, or activate the platform-wide kill switch — including in response to suspected abuse, security incidents, legal demands, or violation of these Terms.

A kill action is not a refund. Tokens already minted on Solana remain on-chain and are not unwound. Pending fees that have not yet been distributed at the time of a kill action may be returned to the project treasury, redirected to remaining eligible contributors, or held pending resolution, in our reasonable discretion.

Nothing in GitShipt constitutes financial, investment, tax, or legal advice. Tokens launched on GitShipt are not offered as securities, and no statement on the platform should be read as a solicitation to invest. We make no representation about the value, liquidity, or future performance of any token.

Contributor scores, leaderboards, projected payouts, and historical statistics are informational only. Past payouts do not predict future payouts.

GitShipt may run in local, devnet, testnet, or mainnet mode depending on deployment configuration. Non-mainnet SOL and tokens have no monetary value, and any “USD” figure shown for a non-mainnet project is a synthetic display value.

Because GitShipt is hackathon-stage software, the database, the indexer, and the on-chain state may be reset, migrated, or wiped at any time without notice outside explicitly announced production environments. Mainnet activation is controlled by production readiness gates and is not implied by a local or preview deployment.

You agree to indemnify and hold harmless the GitShipt team and contributors from any claim, loss, or expense arising from your use of the service, your launches, your repository's contents, or your violation of these Terms.

To the maximum extent permitted by law, GitShipt and its contributors are not liable for any indirect, incidental, consequential, or punitive damages, or for any loss of tokens, missed payouts, RPC failures, or third-party outages (including GitHub, Bags.fm, Helius, Vercel, and Neon). Aggregate liability for any direct claim is capped at one hundred U.S. dollars (USD 100).

These Terms are governed by the laws of the State of Delaware, USA, without regard to conflict-of-laws principles. Any dispute that cannot be resolved informally shall be settled by binding individual arbitration seated in Delaware. You waive any right to participate in a class action.

We may update these Terms at any time. The “last updated” date at the top of this page reflects the most recent revision. Material changes will be announced in the product or via the project repository. Your continued use of GitShipt after a change constitutes acceptance of the updated Terms.

Questions, security reports, and abuse complaints: legal@gitshipt.com. Bugs, feature requests, and source-level discussion happen in the public repository at github.com/SYMBaiEX/gitshipt.