Create Reward
MaintainerThe maintainer creates a USDC reward linked to a GitHub Issue via the PullPay interface. Funds are locked in Soroban escrow.
Contributors can see that the reward exists on-chain before they start working.

Automated contributor rewards on Stellar
by Contributor
Reward Amount
37.25 USDC
Stellar Network
Locked
Maintainer funded
Merged
PR verified
Settled
USDC sent
Maintainer
GBXF...7Q3K
Contributor
GDN...4KJ2
No custody.
GitHub APIs enforce payouts.
Bug fixes, docs, translations,
and ecosystem growth.
Fast, low-cost, and
developer friendly.
The Problem
Open-source ecosystems depend on hundreds of small contributions: bug fixes, documentation updates, translations, and developer tooling improvements. Yet rewarding these contributions is surprisingly difficult.
For a $5–20 reward, maintainers often coordinate payouts manually through Discord, spreadsheets, direct messages, and wallet collection. The administrative overhead frequently exceeds the value of the reward itself.
As a result, many valuable contributions go unrewarded. PullPay automates the entire settlement process through GitHub workflows and Soroban escrow.
2.9% + $0.30 fee — 36% erosion on a $5 reward.
Account freezes. Geographically restricted.
$15–$45 overhead. 3–5 day settlement delay.
$15+ gas fees. Micro-rewards are economically dead.
Ecosystem Gap
Stellar already supports grants, hackathons, and ecosystem funding.
What is still missing is reusable infrastructure for rewarding everyday contributions:
Fixing bugs
Improving documentation
Maintaining SDKs
Translating resources
Supporting community tooling
PullPay fills this gap by connecting GitHub contribution events directly to Soroban-based reward settlement.
Verifiable settlement from GitHub to Stellar
The maintainer creates a USDC reward linked to a GitHub Issue via the PullPay interface. Funds are locked in Soroban escrow.
Contributors can see that the reward exists on-chain before they start working.
The maintainer adds a single `pullpay.yml` GitHub workflow file to their repository. You can choose Instant Payouts or a 24-hour Timelock for a dispute window.
One file. No SDK, no API keys, no complex integration.
When a contributor submits a PR, the maintainer reviews and merges it. The GitHub Action triggers the Cloudflare validation layer, which verifies the merge and tells the Soroban contract to release USDC.
Merge the PR → payment is automatic.
Why Stellar
Contributor rewards are often small — sometimes only $5–10. Traditional payment rails make these rewards inefficient because fees can consume a significant portion of the payout. Stellar enables economically viable contributor rewards through:
$5 micro-rewards remain $5. No fee erosion.
Stable, real-world value. No volatile tokens.
Programmable escrow — funds locked upfront, released on merge, refunded on timeout.
The moment a PR is merged, USDC arrives in the contributor's wallet.
Removes geographic barriers common in traditional payment systems.
Stellar & Soroban
Low fees. Contract release. Visible state.
Global, near-instant settlement for contributor rewards.
Native USDC
Stellar Asset Contract eliminates token wrapping. Direct USDC transfers cost a fraction of a cent without needing approvals.
Escrow rules execute on-chain.
SEP-7 / Pre-flight
Cost
Micro-rewards made viable.
Architecture
PullPay relies on three core components. The GitHub Action only notifies — the Worker independently verifies via GitHub API and the contract enforces per-reward release limits.
Built with rs-soroban-sdk. Interfaces natively with SEP-41 (Stellar Asset Contract) to lock USDC upfront and handle automated releases and timeout refunds.
A pullpay.yml workflow utilizing @actions/core and a Cloudflare Worker oracle. Settlement requests are authenticated via workflow executions and verify PR merges.
The worker verifies the merge via GitHub API, then triggers the Soroban contract via @stellar/stellar-sdk using ephemeral, allowance-limited keys.
Ecosystem Impact
PullPay introduces Stellar through a workflow developers already understand. Instead of asking contributors to learn blockchain first, PullPay embeds Stellar directly into the contribution process.
Every successful reward creates:
A funded Stellar wallet
Every contributor who claims a reward creates or funds a Stellar wallet.
A USDC transaction
Each settlement is a real USDC transaction on the Stellar network.
A Soroban contract interaction
Every reward release is a Soroban contract interaction.
A developer exposed to Stellar
For some contributors, this may become their first practical interaction with Stellar.
PullPay turns contribution activity into measurable ecosystem activity.
Use Cases
PullPay is designed for any scenario where small, verifiable contributions need to be rewarded quickly and efficiently.
Stellar SDK maintainer posts $20 reward for a bug fix. Contributor submits PR. On merge, $20 USDC is released automatically.
Community program offers $5–$10 for documentation improvements. Only viable because Stellar fees are <$0.01.
Organizer pre-funds rewards via Soroban escrow. Winners are paid automatically when their code is merged.
Chapter leads run transparent bounty campaigns with verifiable on-chain settlement.
FAQ
Everything you need to know about how PullPay works.
Timing
Stellar continues to invest in developer tooling, grants, hackathons, and ecosystem growth. As more projects launch on Stellar, contributor incentives become increasingly important.
PullPay explores a reusable infrastructure layer that allows ecosystem projects to reward open-source work using the same programmable financial rails that power the broader Stellar network.
Start now
PullPay converts GitHub contributions into on-chain Stellar activity. Trust-minimized settlement built for the Stellar ecosystem.