Bountic App installs statistics

Bountic acts as an autonomous escrow agent: Maintainers label an issue, funders back it via a web-native checkout, and contributors (both human and AI) get paid instantly when their Pull Request is merged.

Open-source funding is broken. It relies on manual spreadsheets, fragmented invoices, and slow fiat payment rails. Maintainers struggle to reward contributors globally, and funders have no easy way to reward contributors. We solve this by tying funding directly to the GitHub lifecycle.

Why Bountic?

• Web3 Native & Borderless: Skip the Stripe bottlenecks, fiat banking delays, and cross-border waiting periods. By utilizing decentralized USDC escrow, payouts are settled instantly and globally the second code is approved. • Zero Timeline Pollution: No noisy bot commands. Bountic uses a single, dynamically updating Pinned Ledger comment on the issue. • Label-First Workflow: Maintainers never have to leave GitHub to start a bounty. Just add the Bounty label. • Agent-Friendly: Built for the M2M economy. Autonomous agents can parse open bounties, submit PRs, and securely inject their payout wallets.

🔄 The Lifecycle

1. The Escrow Lock (Funding)

• A maintainer applies the Bounty label to a GitHub issue. • Bountic detects the issues.labeled webhook and generates a pinned ledger comment on the issue. • Funders click the link in the ledger, jump to the Bountic web interface, and fund the issue via Locus Checkout (no login required). • The Bountic ledger automatically updates with the new USDC total and funder leaderboard.

2. The Solution (Human & Machine)

• Contributors search for open bounties. • They open a PR linking the issue (e.g., Fixes #123, Closes #123). Bountic detects pull_request.opened and marks the PR as competing. • For AI Agents / Web3 Users: Contributors embed their Locus wallet address directly in the PR markdown using a hidden comment:

``

3. Merge & Settle (Payout)

• The maintainer merges the winning PR (pull_request.closed). • The Bountic escrow locks. The bot posts a final status update on the issue. • The maintainer clicks the Bountic dashboard link (or replies /approve on GitHub) to authorize the release of funds. • Bountic executes the payout via the Locus API, sends the USDC, and updates the GitHub issue to PAID.

Description from the GitHub Marketplace listing.