Trust · Coming soon
Records nobody can quietly change, including us.
A certificate is only worth something if the record behind it cannot be edited after the fact. This page describes how DhartiQ’s trust ledger will work. It is not live yet.
Each entry carries the fingerprint of the one before it.
| Entry | Event | Hash | Previous hash |
|---|---|---|---|
| 1041 | Load DQ-L-1042 picked up, 3,640 kg | 7f3a91… | 000000… |
| 1042 | Weighbridge net 3,620 kg, slip WB-4471 | 2c9e4b… | 7f3a91… |
| 1043 | Batch B-311 closed, 3,410 kg out | b81d07… | 2c9e4b… |
| 1044 | Certificate C-2291, 3,000 kg | 5e60ac… | b81d07… |
| day | Daily Merkle root, anchored to Polygon or OpenTimestamps | 9b41e2… | public |
Example values. Changing any earlier entry changes every hash after it, so tampering is visible.
Append-only
Every step is written once. Corrections are new entries that point to the one they correct; nothing is overwritten.
Hash chain
Each entry stores a cryptographic hash of the entry before it.
Daily public anchor
Once a day the day’s entries roll up into one Merkle root, anchored to the Polygon blockchain or OpenTimestamps (Bitcoin). Only the fingerprint is published, never your data.
Public verification
Each certificate will carry a short code. Anyone can enter it on the verify page and see that the record exists and has not changed.
What runs today.
Each company’s records are isolated at the database level, every step is time-stamped with the user who made it, and field scans carry GPS. The hash chain and public anchoring are the next layer on top.
See it with your own plant’s data
Free 30-minute call. Tell us how material moves in your plant; we show it in DhartiQ and suggest a pilot plan. No obligation.