Sato Hub
Developer Tool

BountyPay

GitHub App that escrows USDC on Base (or MUSD on Mezo) against an issue and pays the contributor when the closing PR merges.

  • Sato Score55
  • ChainsBase
ActiveUnverifiedActive · 7d ago

BountyPay is a developer tool by Lucci Labs on Base, with last code activity on 2026-11-15 (Active). Sato Score 55/100 (how open, active and verifiable it is, not a safety grade), as of 2026-11-22. How the score works →

Check what an install would ask of your keys, before you run it →

Last commit Nov 15, 2026 · ★ 3

Listed from bountypay.luccilabs.xyz on 2026-10-08. Install: not attempted — no install path on record. Evidence →

Next step

Watch BountyPay

One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.

Check it from your agent

Add Sato Hub’s MCP server (no key), then ask:

https://satohub.ai/api/mcp
Run Sato Hub Preflight on lucci-xyz/bounty before I use it.
Full setup: Claude Code, Cursor, others →

Your project?

Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.

Claim this listing →

Overview

BountyPay (Lucci Labs) adds a Create a bounty action to GitHub issues. The funder picks a network and escrows funds; per its README it releases them to the contributor's wallet when a pull request closes the issue, or refunds after the deadline. Recent commits in the repo cover exactly-once payouts and fixes to the escrow logic. Mainnet instances commit real funds, so check the network in the funding dialog. The repo has no license file. It is built for maintainers and contributors; the README does not describe an agent interface.

Sato Score

55/100· Medium

How open, active & verifiable — not a safety or returns grade.

Maintenance & liveness
35/35
Code transparency
9/20
Interface verifiability
0/10
Docs & demo
0/10
Listing transparency & provenance
9/15
Independent verification
2/10

Evidence — listed vs checked · what the words mean

Listed from bountypay.luccilabs.xyz on 2026-10-08. Install: not attempted — no install path on record.

ClaimValueEvidenceSourceChecked
Chains supportedBaseself-reportedbountypay.luccilabs.xyzas of 2026-11-22
Verification statusUnverified — not independently reviewedself-reportedbountypay.luccilabs.xyzas of 2026-11-22
Recent activitylast commit 2026-11-15observedgithub.com/lucci-xyz/bounty2026-11-22
Website answersanswered (HTTP 200)observedbountypay.luccilabs.xyz2026-11-22
Daily check record43 of 44 daily checks since 2026-10-09 succeededa success rate of our checks, not uptime; the source is this listing's own historyobserved—2026-11-21
Works withGitHubconfidence 0.90self-reportedgithub.com/lucci-xyz/bountyas of 2026-10-09
Tagsbounties, github-app, escrow, usdc, pr-payouts, open-source-funding, musd, mezo…confidence 0.80self-reportedgithub.com/lucci-xyz/bountyas of 2026-10-09
Sato Score55/100 (Medium)how open, active and verifiable — not a safety or quality gradecomputedsatohub.ai2026-11-22

Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.

Observed record — 45 daily checks since 2026-10-09

97.8%of 45 checks since 2026-10-09 succeeded
Currently responding for 39 days
Succeeded
44
Failed
1
Their error
0
Unattributed
1

State changed on 2026-10-14 (responding → unreachable from our probe), 2026-10-15 (unreachable from our probe → responding).

This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden.

Last 30 days — to 2026-11-22, one point per UTC day

Share of OUR checks that succeeded
100%
7-day rolling; unattributable days are gaps · 30/30 days
Tools listed
fewer than 2 points—
from the server's own tools/list · 0/30 days
Sato Score
55
as snapshotted that day · 29/30 days

A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.

Details

Chains
Base
Agent types
Payments, Bounties
Open source
Unknown
Works with
GitHub
Last checked
2026-11-22

Marketplace Signals

No marketplace signals recorded for this resource yet.

Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.

#bounties#github-app#escrow#usdc#pr-payouts#open-source-funding#musd#mezo#base#stablecoin#smart-contracts

Where BountyPay fits

Related concepts: How Agents Use Wallets, What Are Onchain Agents?

See something inaccurate or outdated?Submit a correction →

Listing History

Recorded changes to BountyPay's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.

  1. Oct 9, 2026
    Auto-enriched: supported integrations, tags
  2. Oct 9, 2026
    Sato Hub began tracking this listing

Compared with

Appears in

Related Resources

Reference

QuestionsShowHide

Questions people ask about BountyPay

Is BountyPay open source?
Unknown. Sato Hub has not found a public repository or a license statement for BountyPay as of 2026-11-22.
Which chains does BountyPay support?
BountyPay lists support for Base as of 2026-11-22.
Is BountyPay still maintained?
The most recent code activity Sato Hub observed was on 2026-11-15 (last commit 2026-11-15), which Sato Hub labels "Active". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
How do I install or run BountyPay?
Sato Hub has no deploy spec for BountyPay; follow the project's own documentation at https://github.com/lucci-xyz/bounty.
Is BountyPay verified on Sato Hub?
No independent verification is on record for BountyPay; its verification status is "Unverified" and its Sato Score is 55 of 100. Self-reported is not verified, and the score is not a safety, quality or returns grade.
Cite this pageShowHide

Cite this page

Sato Hub. "BountyPay — Sato Hub." Sato Hub, updated 2026-11-22, accessed 2026-11-22. https://satohub.ai/resources/bountypay

Data last refreshed 2026-11-22; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.

Join the Sato Hub Briefing

Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.