Skip to content
QIRO

Protocol

Claim ↔ Reference.

Qiro Protocol pairs every on-chain claim with the underlying reference it settles against. Claim data and reference data are displayed side-by-side together with their respective age, so settlement context, freshness, provenance and synchronisation can be inspected directly from the interface — on Robinhood Chain.

Philosophy

A claim exists. A reference exists. Qiro puts them next to each other and shows how old each one is.

06How Qiro settles

Three reads. One verdict.

Nothing in the interface is a decoration for a process that happens elsewhere. Each step is a real read, and each read can fail visibly.

  1. 01

    A claim is observed

    A tokenized claim is read from the Qiro registry: issuer, contract, value, quantity, block and timestamp. The timestamp starts the claim clock.

    getClaim · getBlock

  2. 02

    Its reference is resolved

    The claim names the reference it settles against. Adapters resolve it — registry, HTTPS attestation, oracle feed or manual pin — and normalise the answer. No answer is reported as REFERENCE UNAVAILABLE.

    onchain · api · oracle · manual

  3. 03

    Alignment is evaluated

    Values, timestamps, availability and settlement state are compared on one clock. The verdict is ALIGNED only when everything agrees; otherwise PENDING, STALE REFERENCE, VALUE MISMATCH or UNKNOWN.

    age Δ · tolerance bps · thresholds

Settlement alignment

Six states. One is a verdict.

Only ALIGNED asserts anything. Tolerance 10 bps · fresh 0 – 5 min · aging 5 min – 30 min · stale 30 min+.

  • ALIGNEDValues agree within tolerance, the reference is available and within the fresh/aging window, and the claim is settled.
  • PENDINGThe claim has not reached a settled state, or is under dispute.
  • STALE REFERENCEThe reference exists but its last observation is older than the stale threshold.
  • VALUE MISMATCHClaim and reference values differ by more than the configured tolerance.
  • REFERENCE UNAVAILABLENo reference is linked, or every configured adapter failed to return it.
  • UNKNOWNA timestamp, value or currency could not be established. Qiro never guesses.

07Settlement strand

Two paths. Bridged where both were seen.

The upper strand is the claim; the lower strand is its reference. A bridge appears only where an observation exists on both sides — gaps are gaps.

ClaimReference

Bridges = paired observations · fade = not yet observed

SVG · CSS · no WebGL

Trust rule

Nothing is verified by default.

Where data is missing the interface says so: REFERENCE UNAVAILABLE, AGE UNKNOWN, UNVERIFIED. Demo data is only ever shown with a DEMO label, and demo records never link to the explorer.

Current data mode

demo

Registry

unset

Reference API

unset

Explore claims Integration docs