Receiz/Trust Center

Canonical Trust Surface

Receiz publishes the canonical trust surface for independent verification across files, documents, media, and package formats. Original file bytes remain authoritative, the offline verifier is the reference runtime, and API routes are optional mirrors for convenience and automation.

trustcanonical
verificationoffline
signingActive
realmpublished
Back to homeOffline verificationOpen Offline VerifierVerify files on-device without network dependency.Download Offline VerifierHTML file for local offline use.html
Authority model

What is authoritative

Verification behavior is anchored to file bytes and reference verifier behavior across all supported file carriers.

Artifact bytes define the verdict

The file is the source of truth. Verification starts with exact bytes for PNG/PDF/SVG/JSON/media/package artifacts, never screenshots or OCR.

Offline verifier is the reference implementation

Decision behavior can be reproduced fully on-device without network calls, enabling resilient validation during outages.

Offline signing trust modes are explicit

Global offline trust mode uses approved local signing material and signature v4 cert-chain policy checks to keep files verifiable across devices offline, without account sign-in requirements. Untrusted device-only signing stays off by default.

Online API and /v routes are mirrors

Public routes improve sharing and automation, but they never replace original-file trust.

Trusted verdict requirements (v24)
  • A trusted Receiz signature v4 must be present and pass payload-hash, root-key policy, device cert-chain, cert validity, and signature verification checks.
  • Proof must be a real g16: Groth16 envelope.
  • Anchor data must be present and match code/pulse identity.
Machine contract: /standards/receiz.trusted-profile.v1.json
Offline verification remains available during outages.

If Receiz is offline, verification continues from the file using the local verifier runtime.

Record and Seal also run offline with trusted local signing material. No account is required for Record, Seal, or Verify.

Open Offline Verifier
Audit bundle

Published reference values

These values are designed for independent checks.

Signer key ID
de26d7eb2fb3Active
Canonical origin
https://receiz.com
RP-ID
receiz.com
How to audit (minimal)
  1. Obtain the file (or sealed package ZIP), not a screenshot.
  2. Load the file in the offline verifier (or upload package ZIP/folder to Verify).
  3. Confirm decision and compare canonical realm values.
  4. Use standards and test vectors for conformance checks.
Live status and incidents are public.
WireProof, Receiz Core, PresenceBound, and AssetSeal route health are continuously published with active incident state.
Open live status page
Signing
Active
Signer key ID: de26d7eb2fb3
Verification realm
Canonical
https://receiz.com
RP-ID: receiz.com
Availability
Offline verifier
Online routes publish live status.Offline verification runs without network.Open Offline Verifier
Incident log
Live
Public status surface for WireProof + Receiz Core + PresenceBound + AssetSeal routes, including active incident publication.
Open live status
Standards
Public conformance artifacts

Canonical schemas for proof bundles, carrier/envelope contracts, Groth16 envelopes, and document/package verify API responses, plus stable error codes and test vectors used across independent implementations.

schema·trusted profile·bundle schema·groth16 envelope·document + package verify schema·error codes·test vectors
Generated
2026-03-07T08:32:01.877Z
Reference verifier

Verify original bytes on-device

The offline verifier is the deterministic reference for decision behavior.

Offline Verifier instrument
Offline verification for sealed files.