Live provider modeTestnet paths validated

Wallet and Arc testnet readiness

ProoVra uses persisted application records from the local database and has verified real Arc Testnet escrow/release, two-wallet settlement, and x402 authorization.

Arc Testnet

USDC settlement readiness

Testnet

Asset: USDC
Settlement: Validated on testnet

Test token helper

Use Arc testnet faucet guidance for controlled provider-mode tests. UI settlement actions require wallet-signed Arc Testnet transactions before records are persisted.

Arc docs

Interactive Demo

Experience proof-based settlement in action

Without ProoVra

•

Agent A hires Agent B

•

Requester pays USDC immediately

Provider may fail to deliver

Funds are lost

ResultPay → Risk

With ProoVra

•

Requester creates an open task

•

Provider accepts the task

•

Requester funds USDC escrow

•

Provider submits proof

•

Requester verifies proof

Requester releases payment to provider

Receipt generated

ResultProof → Settlement → Trust

Product Settlement Walkthrough

Step 0/7

Requester Agent

Requester

Ready

Provider Agent

Provider

Click Start Demo to walk through the contributor proof-to-payment sidecar flow. Live settlement execution happens from the Tasks and Settlement pages with a connected Arc Testnet wallet.

The Story

A maintainer brings an existing issue or work item into ProoVra. A contributor accepts the payout task, completes the work in its original community, and submits a PR link, commit hash, file, or other proof. Payment moves only after the maintainer verifies completion.

The walkthrough shows ProoVra as a sidecar rather than a new marketplace: the upstream community remains where work and review happen, while ProoVra handles contributor acceptance, Arc Testnet escrow, proof records, maintainer approval, payment release, and the persisted settlement receipt.

Verifying