Check the approved record.

The planned workflow gives recipients a shared reference for the approved version. A checkpoint and a file comparison answer different questions.

• Buyer: open the QR link on the paperwork to read the checkpoint’s approvals, publication and record history. The QR link alone does not compare evidence files.
• Auditor: calculate the fingerprint of the supplied evidence bundle and compare it with the approved snapshot, then review the same published history.
• A matching file can still belong to a corrected or disputed record. Read the comparison and the record’s status separately.

The first three steps keep the evidence inside the private platform. Publication creates a reference that authorised recipients can check against their own files.

• 1. Record — Capture custody, assay and export records in the platform.
• 2. Freeze — Fix a snapshot at an agreed milestone with a clear cut-off time.
• 3. Approve — Operations and evidence review each approve that snapshot with a separate key.
• 4. Publish — The planned Chainlink CRE delivery carries the fingerprint and minimal metadata to Blockdor’s evidence registry. The registry enforces approval and record-history rules.
• 5. Check — Read the checkpoint, compare files when supplied, and review the approvals and published history.

A fingerprint protects the integrity of an approved record. Assays, custody documents and the people responsible for them remain essential to assessing the gold.

• File match: supplied files match the approved snapshot’s fingerprint. This does not establish that their contents are accurate or complete.
• Approvals: two distinct roles approved the snapshot with separate keys. This does not establish independent investigation or freedom from mistakes.
• Publication: the fingerprint was published by the recorded time. That timestamp does not establish when a physical event happened.
• History: published corrections or disputes can be read. The public record cannot show a newer dispute that has not yet been published.

Weights, documents, locations and counterparties stay in Blockdor’s private platform. Evidence files are shared with authorised recipients, such as a buyer or an auditor.

• The public reference is designed to contain the fingerprint, record status, role approvals and publication timestamp.
• Public fields are being reviewed individually because timing and counts can also reveal activity.
• The evidence registry covers record approval and publication. It involves no tokens, payments or escrow.

In the planned workflow, a correction creates a new version linked to the earlier one. The earlier version and its approvals remain visible. A dispute is published against the relevant record.

• For a corrected record, request the replacement files and compare them with the new checkpoint.
• For a disputed record, review the evidence and contact the record provider. A matching fingerprint does not resolve a dispute.
• If the checkpoint is unavailable, no comparison or latest-history result can be confirmed.

The verification workflow and contract approach are defined. Implementation is the next step.

• Test-network pilot: begin with one approved snapshot checked from exported files, then add public publication, corrections and disputes.
• Chainlink delivery: the pilot is planned to publish directly first. Chainlink CRE delivery follows access approval and integration.
• Production publication: follow an independent contract review. The planned file check is designed to work without Blockdor’s website; checking the latest history still requires access to the public record.