Turn GitHub issues into funded bounties. Reward open source contributions through GitHub workflows and Solana payments.
I co-founded GitWork and was responsible for its architecture, full-stack development, deployment and maintenance. The platform onboarded 5+ projects and paid out $1K+ in Solana bounties during its first three weeks.
GitWork is a retired project, preserved here as a portfolio and technical reference. This repository contains the latest application implementation, including its original interface and integration flows. The hosted service is retired, and the former domain is no longer owned by this project. Links in this repository point to the source code or use explicit self-hosting examples.
Running the full application requires your own GitHub, Privy, Solana, and optional browser integration configuration. No production credentials or user databases are included.
- A repository owner adds a label such as
gitwork:USDC:50to a GitHub issue. - The GitHub App processes the label and creates a bounty with a dedicated escrow wallet.
- A deposit monitor confirms funding and updates the bounty listing.
- A contributor submits a pull request referencing the issue.
- Once the pull request is merged, the contributor can claim the reward.
The implementation includes GitHub OAuth, contributor profiles, managed user wallets, earnings history, withdrawals, configurable fees, refunds, token price estimates, and optional Discord funding notifications. Bounty labels support SOL and allowlisted SPL tokens; internal wallet withdrawals support USDC and SOL. Legacy octavian: labels remain supported.
| Layer | Stack |
|---|---|
| Frontend | React 18, Vite, React Router, Tailwind CSS |
| API | Node.js, Express, Passport, Octokit |
| Storage | SQLite with better-sqlite3 |
| Wallets and settlement | Privy, Solana web3.js, SPL Token |
| Supporting integrations | CoinGecko pricing, Discord webhooks, EmailJS |
Use Node.js 22 or newer and npm. The native SQLite dependency may require compiler tools if a prebuilt binary is unavailable for your environment.
# Install the backend and frontend dependencies
npm ci
npm --prefix gitwork-front ci
# Copy the safe configuration templates
cp .env.example .env
cp gitwork-front/.env.example gitwork-front/.env.localConfigure your own credentials in the local environment files. Generate independent session and webhook secrets, for example with openssl rand -hex 32. Set GITHUB_PRIVATE_KEY_PATH to a locally stored GitHub App private key, and configure OAuth callback and claim URLs for your environment.
# Initialize storage and start the backend
npm run db:migrate
npm run devIn another terminal, run the original frontend:
npm --prefix gitwork-front run devThe original Vite configuration and backend both default to port 3000. If running them separately, choose another frontend port, such as npm --prefix gitwork-front run dev -- --port 5173, and configure the API and OAuth URLs for the setup you are testing. For a same-origin deployment, build the frontend and serve it through the Express production configuration.
npm --prefix gitwork-front run build
NODE_ENV=production npm startThe example RPC and USDC mint use Solana devnet. Other allowlisted token mint addresses are historical mainnet configuration: review mint addresses and cluster compatibility before enabling those currencies.
Browser settings beginning with VITE_ are public. Keep GitHub App private keys, OAuth secrets, Privy secrets, RPC credentials, and wallet private keys in server-only configuration. Set PLATFORM_REVENUE_WALLET to a public wallet address explicitly.
| Path | Purpose |
|---|---|
gitwork-front/ |
Original application interface |
src/routes/ |
Webhook, authentication, bounty, claim, wallet, and fee endpoints |
src/services/ |
GitHub, Privy, Solana, deposit monitoring, pricing, and Discord |
src/db/ |
Database schema and migrations |
src/config/tokens.js |
Supported token configuration |
docs/ |
Product flows and implementation references |
archive-site/ |
Existing retired-project landing page |
- Repository owner flow
- Contributor flow
- Wallet flow
- Fee system
- Quick reference
- Visual flow
- Security notes
Detailed flow documents describe the retired service and may refer to its former hosted endpoints.
# Compile the frontend
npm --prefix gitwork-front run build
# Scan the full Git history with Gitleaks installed
gitleaks git . --log-opts="--all" --redactThe original npm test command auto-discovers scripts that exercise wallet transfers and webhooks. These are integration scripts, not an offline test suite; inspect and configure them before running. A successful frontend build does not validate payment settlement.
This is historical application code, not an audited payment product. It uses server-controlled wallets rather than a trustless escrow smart contract. Review authorization, session handling, payout idempotency, concurrent withdrawals, amount validation, token configuration, and refunds before considering any deployment with real funds.
