Docs for contributors

GitShipt mints a token on Bags.fm. Every trade on that token generates fees. 5.0% goes to the GitShipt platform; the remaining 95.0% is the contributor pool.

Once a day at 00:30 UTC, the platform refreshes the Bags-native contributor split based on the latest leaderboard snapshot. The split is tier-weighted: 30% to rank 1, 20% to rank 2, 15% to rank 3, and the rest allocated across ranks 4-10.

Claiming happens in Bags. Use the GitHub identity that appears on this leaderboard, connect your wallet in Bags, and sign the claim transaction there. GitShipt keeps snapshots and BPS rebalances auditable; it does not custody contributor SOL.

You don't need to do anything per-cycle on GitShipt. The cron job keeps the Bags fee-share BPS aligned with the latest frozen snapshot.

This project uses the GitShipt v0 scoring formula:

score = 3 × mergedPRs
      + 1 × commits
      + 1.5 × reviews
      + 0.5 × issues
      + 0.2 × log10(1 + netLines)

• Window: 30 days. Older contributions are weighted by linear decay.
• Self-merged PRs are weighted 0.5×.
• Bot accounts (/^(.*-bot|dependabot|.*-ci|renovate)$/) are excluded.
• Project-specific blocklist: dependabot, renovate-bot, github-actions

Top 10 contributors get paid each cycle. Minimum daily pool to fire a payout: 0.1000 SOL.

Open a pull request on SYMBaiEX/gitshipt. Once it merges, it counts toward the next snapshot at midnight UTC. Commits to the default branch count too.

Want repo-specific contribution guidelines? Check the project's CONTRIBUTING.md on GitHub.

• What if I don't have a wallet? Connect one in Bags before claiming. Project owners can update claimers as contributors onboard.
• Can scoring change? The owner can adjust weights and the topN. Each snapshot stores its formula version, so historical payouts are reproducible.
• Where do I see my earnings? Open your earnings dashboard.
• Where do I report abuse? See the platform docs for moderation contact.