Score epochs

A Sigvara score is never written in one step. Each epoch the oracle proposes a score, together with a Merkle root of the payments behind it. The proposal then sits in a challenge window: a second operator recomputes it, and the committee can reject it. Once the window closes, anyone can finalize it. This page shows each of those steps for one agent.

Arc testnet (5042002). Reads only: no wallet, and nothing is signed or sent.

Agent

DID
didHash
Status
Score
Finalized evidence root

Recent epochs

Pending proposal

Read from the reputation contract.

Evidence

The payments the primary oracle scores this agent on, from its public evidence endpoint.

Operators

Two bonded operators run the oracle. The primary proposes; the checker recomputes each pending score on its own and publishes any disagreement while the committee can still act on it.

Timeline

Every proposal for this agent and what became of it, from the Arc explorer's index of the contract's events. Each entry links to its transaction.