A weighing record that carries its evidence.

What makes a weighing record verifiable?

A printed number is easy to read but offers limited evidence about its history. A verifiable record includes information that can be checked against the retained data: a fingerprint, a digital signature, and the context needed to interpret the result.

MetraCrypt connects measurement records with operator, equipment, customer, and transaction details. Signed history and integrity checks help reveal changes to retained records. Reasons for corrections and cancellations make the sequence more useful to someone reviewing a disputed transaction.

Three different questions, three different checks

Signer identity depends on an independently trusted signer registry. A signature can be checked mathematically without establishing that an unfamiliar signing key belongs to the person or organization someone claims it does.

Keep correction history useful

Operational errors happen: the wrong customer is selected, a vehicle identity is mistyped, or a ticket needs cancellation. A useful audit trail preserves what was recorded, what changed, who made the change, and why. Quietly replacing an earlier value removes context that a reviewer may need.

Connect the correction to the transaction and retain its reason. When presenting an exported record, explain which version it represents and provide the relevant history for the review. The goal is a readable chain of events supported by evidence.

Optional anchoring, with business records off-chain

The anchoring add-on batches records and submits cryptographic commitments using Solana and Bitcoin through OpenTimestamps. The commitment is separate from the underlying business records. Core integrity capabilities do not require the anchoring worker.

Anchoring evidence provides an external time bound for a commitment when successfully verified. It does not establish an exact physical capture time. Anchoring can pause while core capture continues, provided the MetraCrypt service remains reachable.

Portable evidence and independent review

MetraCrypt exports portable proofs for a standalone verifier. The verifier can check the signed record, its inclusion in a batch, and available anchoring evidence without requiring a MetraCrypt account or a paid anchoring add-on.

Integrity evidence does not certify physical accuracy, the truth of manually entered details, or regulatory approval. Exported proofs can contain business data, so choose the information and recipients needed for the review.

Explore the ticketing workflow or use our buyer’s guide to evaluate record history during a demonstration.

What does the example ticket’s hash check prove?

The example scale ticket recomputes a SHA-256 fingerprint from its embedded sample record and compares it with the displayed hash. A match shows that those sample bytes match that fingerprint. The example does not check a digital signature, a signer’s identity, or a blockchain anchor.

A hash stored beside a record is not an independent source of trust. Someone able to replace both could publish a different record with a new matching hash. For a real review, obtain the reference evidence through a trusted source, check the signature against an appropriately trusted signing key, and examine any claimed anchoring evidence separately.

1. Identify the record and version. Match the transaction ID and correction history to the ticket under review.
2. Establish the trust source. Confirm how the expected fingerprint or signer key was obtained, rather than trusting only a badge displayed with the ticket.
3. Read the verification result by layer. Distinguish a hash match, a valid signature, batch inclusion, and a verified external time bound. Missing evidence is not a successful check.
4. Review the measurement separately. Use equipment and operating records to assess the physical weighing; a cryptographic match cannot perform that assessment.

For background on signing-key and identity assurances, see NIST’s guidance for digital signature applications. This reference explains the underlying trust questions; it is not a certification or endorsement of MetraCrypt.