DRanking Service Receipts
Rings 1.0 ships the cryptographic foundation for DRanking:
a domain-separated, countersigned service receipt (rings-service-receipt-v1) for authenticated
liveness probes, paired with crash-consistent local evidence collection and persistence. This
1.0 vertical slice establishes portable cryptographic attestation and bounded evidence storage
that power the full epoch ledger, trust algebra, and verifiable reputation system in Rings 2.0.
Probe flow
- The beneficiary sends
ProbeRequestwith a random nonce and a current five-minute epoch. - The provider returns
ProbeOffer. The offer embeds the exact signed request transaction, an exact provider-signed completion transaction, the canonical claim, and the provider’s claim attestation. - The beneficiary verifies the transcript against its one outstanding request, signs the same
claim under the beneficiary role domain, and returns
ProbeAcknowledgement. - The provider verifies the complete receipt under live rules and admits it to its bounded local evidence store.
The canonical claim binds network_id, service kind, provider account, beneficiary account,
epoch, nonce, units, request digest, and completion digest. Provider and beneficiary signatures
use different domains. Roles are account DIDs recovered from delegation proofs, so a
delegatee-key rotation does not change the account role.
The canonical marker and the signing domains name this field layout, so a signature over it cannot be interpreted as another receipt protocol; they carry no version, since the protocol is not versioned before 1.0. The release is still a hard cutover: there is no legacy probe/report decoder, negotiation, or dual format.
Verification boundaries
Cryptographic verification is portable: a later reader can verify the two account roles, the canonical claim, and that each delegated proof was valid at its signing time. Live verification is receiver-local: it additionally requires live delegated proofs and accepts only the current or an adjacent provisional epoch at observation time. Persisted evidence records that observation time, but replaying an old receipt never recreates live-observation status.
The freshness key is (network_id, beneficiary_account, epoch, nonce). The same receipt digest is
a duplicate; a different receipt for an occupied freshness key is a conflict. Receipt bytes may be
evicted, but their fixed-size replay markers remain independently bounded and durable while the key
can still be admitted. If the global or per-beneficiary marker bound is full, a new key fails closed
instead of evicting an active marker. A monotonic replay floor prevents clock regression from
reopening a pruned epoch.
Executable model and refinement
Two native Stateright models define the complete state relation for this provisional slice:
crates/core/src/message/service_receipt/model.rsmodels the request, offer, acknowledgement, pending request, three replay gates, four independent delegated-session lifetimes, proof lifetimes, epoch, retained evidence, and independent freshness occupancy. Its actions cover send/deliver, time advance, loss, duplication, reordering, hard-crash restart, and receipt eviction; its admission outcomes cover commit, replay-capacity rejection, and persistence failure.crates/measure/src/evidence/model.rsmodels admission, exact duplicates, freshness conflicts, pair-local and global pressure, deterministic eviction, invalid record rejection, pagination, replay-marker saturation, clock regression, and hard-crash restart under explicit record, byte, and marker bounds.
The checked safety properties are: admitted evidence was live at its observation instant; only a
complete transcript can be admitted; no admitted digest is admitted twice; receipt and replay-state
bounds always hold; eviction cannot remove duplicate protection for a still-admissible key; restart
preserves every committed marker; capacity and regressed-clock paths fail closed; and provisional
evidence cannot change credit or routing inputs. Reachability properties witness the live happy path
and every admission outcome. No delivery fairness is assumed, so the happy path is reachable rather
than inevitable under loss. Production-refinement checks replay the model states through real
session signatures and through ProvisionalEvidenceStore; the shared native/Wasm tests cover
canonical bytes, claim-field binding, transaction binding, and the live-session boundary.
The finite model bounds time, message multiplicity, candidates, and one crash restart. Cryptographic unforgeability remains an explicit assumption: model checking does not replace verification of the real signing and canonical-encoding implementations, which is why those are separate refinement tests. Delivery actions take prior acceptance of each outer transport envelope as a precondition; the model still checks the embedded request and completion independently from the two claim-role attestations.
Evidence admission is synchronous with the separate evidence snapshot: storage failure rolls the transition back, and success means the receipt plus replay marker survive a process crash. Deleting or replacing that configured store explicitly starts a new collector history and is outside the crash model. The durable storage write is the admission linearization point; evidence queries and other admissions share its serialization lock. Cancellation of an incomplete call may conservatively retain the marker, but cannot admit the key twice.
Storage and 2.0 evolution
The node keeps service-receipt evidence in a dedicated store separate from local peer credit measurements. Native nodes use a file-backed snapshot and browser nodes use a dedicated IndexedDB store. Global and per-account-pair record and byte limits are enforced as strict bounds. Oldest evidence is evicted deterministically while preserving active replay markers. Replay markers have independent global and per-beneficiary bounds, and APIs expose bounded digest-ordered pages and privacy-preserving aggregate counters without DID labels.
Opening the browser evidence store is verified at provider construction so every admitted receipt is backed by durable storage that refines the documented process-crash model. Embedding constructors that run without a durable evidence backend keep liveness probing active while skipping receipt persistence.
In Rings 1.0, local routing and peer quality ordering (CreditRecord and
order_peers_by_quality) operate on direct local observations while service receipts accumulate
cryptographically verifiable evidence. Rings 2.0 builds on this foundation to introduce the
multi-service DRanking trust algebra and epoch ledger with its own dedicated ledger domain.