Protocol Specifications

The protocol establishes a trustless bridge between Originators (Clients) requiring computational or manual labor, and Operators (Workers) capable of execution. Capital is locked programmatically in a smart contract and released strictly upon verification of cryptographic or off-chain proof. The system eliminates intermediaries, discretionary approvals, and settlement friction.

Verification is an autonomous process: the underlying Rialo contract directly interrogates an external verifier API using a native webcall entirely bypassing legacy oracle networks. Execution windows are governed strictly by on-chain timers, negating the need for external keeper bots.

The protocol lifecycle strictly adheres to a deterministic state machine sequence:Open In Progress Under Review Settled /Clawback /Disputed

Protocol Initialization

• Access the /tasks/create interface to broadcast execution parameters.
• Define the required proof vector (e.g., GitHub PR, live URL, compiled binary link).
• Establish a strict execution window (deadline). On-chain timers will auto-execute clawbacks if unmet.
• Select a designated verification engine (refer to Verification Engine architecture below).
• Execute Initialize Escrow Contract to lock $RIALO liquidity.

Verifier Architecture Configuration

The chosen verification engine dictates how the smart contract validates the operator's proof. Standard operations utilize url_exists or github_commit. For proprietary business logic, deploy a custom_webhook and connect your internal endpoint.

Dispute Resolution Escalation

• Access the active pipeline via the Mission Control dashboard while the state is Under Review.
• Trigger the Dispute command and inject cryptographic or contextual reasoning.
• The pipeline halts. You gain manual authority to route payment to the Operator or initiate a Refund.
• Warning: Resolution must occur before the protocol's grace period expires, or funds auto-route.

Queue Interrogation

• Monitor the global execution queue at /tasks.
• Utilize telemetry filters to identify optimal reward/complexity ratios.
• Execute the Claim operation on viable pipelines.
• Post-claim, the protocol locks the pipeline exclusively to your wallet address. Parallel execution is disabled.

Proof Delivery Protocol

• Deliver a publicly verifiable URL. The contract verifier must achieve unauthenticated reachability.
• For GitHub integrations, route directly to the specific Commit SHA or Pull Request URL.
• Ensure payload matches client specifications exactly especially for content_match directives.
• Inject operational logs/notes during submission to expedite dispute resolution if triggered.

Settlement Flow

Upon proof delivery, the Rialo contract fires the verification webhook. If the assertion returns true, $RIALO is routed to your wallet with sub-second finality. If false, the pipeline reverts to Under Review, allowing the Originator to manually intervene.

Provr's verification layer is driven by Rialo's Native Webcall architecture. The L1 smart contract independently executes HTTP requests to external APIs, entirely abstracting away third-party oracle infrastructure.

{
  "taskId": "task_001",
  "workerAddress": "rialo1abc...xyz",
  "proofUrl": "https://github.com/worker/repo/pull/42",
  "clientAddress": "rialo1def...uvw",
  "verifiedAt": 1715000000
}

{
  "verified": true,
  "reason": "PR #42 successfully merged into main",
  "confidence": 99
}