Sato Hub
Developer Tool

MergePay

USDC bounties on GitHub issues, paid when a PR merges, with GitHub's signature checked by a contract on Arc.

  • Sato Score54
EarlyUnverifiedRecent · 1mo ago

MergePay is an open-source developer tool by codeswithroh, with last code activity on 2026-10-12 (Recent). Latest release on 2026-10-12. Sato Score 54/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 Oct 12, 2026 · Last release Oct 12, 2026 (v1.0.1)

Listed from mergepay.fun on 2026-10-08. Install: not attempted — no install path on record. Evidence →

Next step

Watch MergePay

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 codeswithroh/mergepay 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

MergePay (codeswithroh/mergepay) escrows USDC on a GitHub issue. Per the README, when a pull request that fixes it merges, GitHub signs a token and a contract on Arc checks that RSA signature onchain before paying the author. The README reports a deployed mainnet contract, 30 passing contract tests and an MIT license. The repo was created in September 2026 and has a single maintainer, so treat it as early. A different project of the same name (0xNexuz/MergePay, a KeeperHub payout demo on Base) is a hackathon demo and is not this listing.

Sato Score

54/100· Medium

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

Maintenance & liveness
25/35
Code transparency
16/20
Interface verifiability
0/10
Docs & demo
0/10
Listing transparency & provenance
10/15
Independent verification
3/10

Evidence — listed vs checked · what the words mean

Listed from mergepay.fun on 2026-10-08. Install: not attempted — no install path on record.

ClaimValueEvidenceSourceChecked
Chains supportednot statedself-reportedmergepay.funas of 2026-11-22
Verification statusUnverified — not independently reviewedself-reportedmergepay.funas of 2026-11-22
Recent activitylast release 2026-10-12 · last commit 2026-10-12observedgithub.com/codeswithroh/mergepay2026-11-22
Website answersanswered (HTTP 200)observedmergepay.fun2026-11-22
Daily check record44 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
Creator profilehttps://github.com/codeswithrohconfidence 0.80self-reportedgithub.com/codeswithroh/mergepayas of 2026-10-09
Works withGitHub, GitHub Actions, Arc, USDCconfidence 0.85self-reportedgithub.com/codeswithroh/mergepayas of 2026-10-09
Tagsbounties, github, escrow, usdc, pr-payouts, arc, github-actions, oidc, solidityconfidence 0.80self-reportedgithub.com/codeswithroh/mergepayas of 2026-10-09
Sato Score54/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

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

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
54
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
Unknown
Agent types
Payments, Bounties
Open source
Yes
Works with
GitHub, GitHub Actions, Arc, USDC
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#escrow#usdc#pr-payouts#arc#github-actions#oidc#solidity

Where MergePay fits

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

See something inaccurate or outdated?Submit a correction →

Recent Activity

All news →

Releases and posts from MergePay, pulled from its GitHub and X.

Listing History

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

  1. Oct 12, 2026
    New release published
  2. Oct 9, 2026
    Auto-enriched: creator profile url, supported integrations, tags
  3. Oct 9, 2026
    Sato Hub began tracking this listing

Compared with

Related Resources

Reference

QuestionsShowHide

Questions people ask about MergePay

Is MergePay open source?
Yes. MergePay is open source; the repository is https://github.com/codeswithroh/mergepay. Checked as of 2026-11-22.
Which chains does MergePay support?
Sato Hub has no confirmed chain list for MergePay as of 2026-11-22; treat chain support as unknown.
Is MergePay still maintained?
The most recent code activity Sato Hub observed was on 2026-10-12 (last commit 2026-10-12, last release 2026-10-12), which Sato Hub labels "Recent". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
How do I install or run MergePay?
Sato Hub has no deploy spec for MergePay; follow the project's own documentation at https://github.com/codeswithroh/mergepay.
Is MergePay verified on Sato Hub?
No independent verification is on record for MergePay; its verification status is "Unverified" and its Sato Score is 54 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. "MergePay — Sato Hub." Sato Hub, updated 2026-11-22, accessed 2026-11-22. https://satohub.ai/resources/mergepay

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.