Connect a wallet
Connect a Rialo extension or unlock the embedded DevNet wallet. The active address becomes the sponsor for workflows it creates, or the contributor wallet for a claim.
Product walkthroughDevNet / Five steps
Code merged.Value settled.
MergePay is a Rialo-native marketplace for public GitHub pull-request bounties. Sponsors publish a clear brief, contributors prove they authored the target PR, and the sponsor approves the payout wallet before RLO is funded.
THE SHORT VERSION
A programmable escrowfor shipped code.Autonomous settlement · onchain receipts
01 / Product
The product
A bounty that can prove why it paid.
Most GitHub bounties rely on a person or a private backend to coordinate the work, identify the contributor, and decide where payment goes. MergePay moves the terms into a Rialo workflow account: repository, pull request, amount, deadline, and an open claim state are committed before funding.
The contributor verifies the public PR author and signs a claim with the receiving wallet. MergePay detects that onchain claim on the sponsor page, where the sponsor approves it before funding. Funding arms Rialo's native heartbeat: a merged pull request pays the approved wallet automatically, while reaching the deadline first refunds the sponsor automatically.
02 / Workflow
Using MergePay
Five steps from brief to settlement.
Post the bounty
Enter a public GitHub owner, repository, pull request number, amount, deadline, and generated workflow ID. The beneficiary is intentionally left open for a contributor claim.
Claim the PR
The PR author connects GitHub. MergePay compares the authenticated GitHub user ID with the exact public pull request, then the contributor signs a claim record with the wallet that should be paid.
Review, approve, and fund
The sponsor page detects confirmed claims automatically. It shows the GitHub identity, payout wallet, exact bounty terms, claim PDA, and Rialo Scan transaction, then rechecks the public PR author by stable GitHub user ID. If several matching claims exist, the sponsor must choose one explicitly. Approval and funding remain separate transactions, and the beneficiary cannot change after approval.
Watch and verify
Rialo keeps checking after funding. A unanimous merged proof pays the contributor; reaching the deadline first refunds the sponsor. The live workflow updates without a page reload, and the separate Settlements page shows only confirmed paid or refunded outcomes.
03 / Rialo
Why Rialo
The chain is part of the verification loop.
REX can attest external conditions
Rialo REX is the bridge between GitHub's public PR, CI, and review evidence and an onchain callback. MergePay consumes a compact validator report inside the program instead of trusting a private payout server.
Escrow is a program state
The sponsor, approved contributor, amount, deadline, claim proof, and settlement flags live in Rialo workflow accounts. Anyone with the account address can inspect the same state.
Failure stays visible
A missing account, unavailable decoder, mixed report, or non-merged pull request does not become a payout. The program and UI keep uncertain funds locked.
04 / Limits
Be precise about the MVP
Useful today, intentionally bounded.
MergePay is a working DevNet builder submission, not production financial infrastructure. These constraints are part of the design and should remain visible to every user and reviewer.
DevNet only
The active deployment is unaudited and uses test RLO. Do not send production funds.
Public GitHub only
The current REX settlement path reads public PR, CI, and review endpoints. Authenticated private-repository settlement is outside this MVP.
Settlement is asynchronous
The native heartbeat and REX callback run automatically after funding, but DevNet and GitHub response time mean a terminal receipt may not appear instantly. Manual check and refund controls remain idempotent fallbacks.
GitHub identity scope
Contributor claims require read-only GitHub OAuth and an exact author-ID match for a public PR. MergePay does not request repository write access or support private repositories yet.
Rialo and GitHub are dependencies
A slow RPC, unavailable REX path, changed GitHub response, or missing account can delay or prevent a decision.
Rent remains in the account
Settlement returns or pays the bounty amount, while the workflow account retains the reserve required by Rialo.
Embedded wallet is browser-local
The local signer is encrypted in this browser and limited to DevNet. Back up the wallet before moving devices.
05 / Review
For Rialo reviewers
Everything important is inspectable.
Use the app as a live walkthrough, then inspect the same facts from the chain. The current program, real transaction activity, workflow decoder, and terminal states are all exposed without a simulated success layer.
Live wallet-scoped activity
Wallet-scoped paid/refunded history
Fail-closed merge and refund branches
Autonomous payout and refund E2E proven
ACTIVE MARKETPLACE PROGRAM