Rialo-native settlementDevNet / Live workflow

Onchain bountiesfor pull requests.

Fund a public GitHub pull request in RLO. MergePay verifies the contributor and releases escrow when the merge is confirmed on Rialo.

Systems, not promises.Every payout ends in verifiable state.

Public PRAuthor-bound
Rialo REXValidator-attested
MarketplaceProgram deployed
02 / CONTROLLED FLOW

One source of truth

Every state is visible.
Every exit is earned.

The workflow does not infer success. It advances only when the expected wallet signs and Rialo can verify the exact account or GitHub condition.

Active marketplaceRialo DevNet
SETTLEMENT SEQUENCE ONCHAIN LIFECYCLE
  1. 01
    ONCHAIN

    Create

    Commit the PR, beneficiary, amount, and deadline.

  2. 02
    ESCROW

    Fund

    Lock the exact bounty amount in the workflow PDA.

  3. 03
    REX

    Verify

    Rialo checks the locked PR, CI, and review policy.

  4. 04
    CALLBACK

    Settle

    Pay on unanimous policy proof or refund after expiry.

03 / EXECUTION

Internet-native proof

The conditioncomes to the contract.

REX / EXTERNAL SIGNAL

The merge proof enters execution.

Rialo validators request GitHub's PR details plus the selected CI and review evidence. Only unanimous proof of the locked policy can advance settlement.

PR + CI + REVIEWSMP1 / 6UNANIMOUS
PROGRAM ESCROW

Value stays inside the workflow.

The sponsor cannot silently redirect the beneficiary after approving a verified claim.

FUNDED1.000 RLO
TERMINAL STATES

One escrow. Two legitimate outcomes.

A verified merge pays the contributor. An expired, unpaid workflow returns the escrow to its sponsor.

Merge verifiedPaid
Deadline elapsedRefunded
04 / CREATE

Start with one pull request

Attach value to work
that can prove itself.

Define a bounty