Verification & Conformance Status

Live Reference-Implementation Example

View a Live UCE Verification Example

This exact record is a live hosted convenience interface from the CbyUCE reference implementation. It currently displays UCE Record Information; Platform-Recorded Upload Date; Manifest Arweave Block Date; exact UTC technical details; manifest hash; platform public-key reference; raw-manifest access; block-explorer access; and JSON verification data.

The inspected example does not currently display a file Arweave block date or a derived Complete UCE Record Date, so this page does not claim that it demonstrates those fields.

• View the example's raw Evidence Manifest on Arweave
• View the example's manifest transaction in a block explorer
• View the example's JSON verification data

What Technical Verification Determines

A result determines only the checks actually performed with the inputs available at that time. A successful check may determine that:

• a presented file's exact bytes produce the content hash recorded in the manifest;
• the manifest produces the recorded manifest hash under the declared canonicalization method;
• the platform signature validates for the referenced public key and signed payload;
• checked storage references resolve to the data reported by the verifier;
• recorded transaction references and available network-reported dates are internally consistent; and
• specified claimant, work, rights, and creation-date statements are present in the recorded package.

A valid platform signature authenticates the CbyUCE origin and integrity of the signed manifest. It does not, by itself, establish that the claimant personally applied a cryptographic signature or that the claimant's statements are true.

What Technical Verification Does Not Determine

Technical verification does not independently determine legal ownership, authorship, identity truth, originality, copyright eligibility, non-infringement, priority over every other work or claimant, license validity, enforceability of an AI opt-out declaration, admissibility, evidentiary weight, or a legal outcome. Creator, claimant, ownership, creation-date, and rights statements remain recorded assertions unless a separately documented attestation process verifies the relevant fact.

Chronology Labels

• Platform-Recorded Upload Date: the date CbyUCE recorded receiving the upload. The value is included in the signed manifest later submitted to Arweave; it is not Arweave-confirmed.
• File and Manifest Arweave Block Dates: network-reported dates for two separate transactions, when available.
• Complete UCE Record Date: when both block dates are available, the later date may be displayed to indicate when both components had network-reported block dates.

The practical plain-language claim is proof of upload date. Exact UTC values remain available for technical examination. UCE and CbyUCE are not RFC 3161 timestamp authorities, qualified electronic timestamp providers, eIDAS trust services, governmental authorities, or authoritative time sources.

Artifact and Review Status

Until the provider-independent package is published and validated, UCE is described as designed for independent verification. Current records may be inspected through published artifacts and the hosted CbyUCE verification route, but full provider-independent reproducibility is not yet claimed. The hosted interface remains a convenience implementation, not proof that provider independence has been completed.

Abuse, Competing Claims, Corrections, and Key Compromise

UCE does not adjudicate disputes, validate the truth of authorship claims, prevent infringement, enforce rights declarations, remove immutable Arweave records, or guarantee that no earlier creator or work exists.

The public process for suspected unauthorized uploads, impersonation, competing claims, correction requests, legal requests, or possible key compromise is documented in the UCE and CbyUCE Case-Handling Policy. Historical Arweave records cannot be silently altered or removed; where technically and legally appropriate, a later notice or superseding record may provide additional context without rewriting the historical record.