Record integrity
What we can prove, and what we cannot
Traceability is a trust product. A platform that overstates what its technology proves is doing the opposite of its job. This page is the plain-language version: the mechanism we actually run, the exact thing it demonstrates, and the things it does not demonstrate no matter how it is marketed.
Why we do not say “blockchain-secured”
RigoTrace does not write to a blockchain, so we do not describe it as blockchain-secured. We think the phrase is doing very little work in this industry: a record anchored to a chain nobody names, with no contract address and no way for you to look it up, is not more verifiable than a database row. It is the same trust assumption wearing a different word.
What we do run is narrower and, we think, more useful: we anchor passport fingerprints into Bitcoin via OpenTimestamps, purely as a timestamp. There is no Agririgo token, no smart contract, and nothing about your crop is written to any chain. Only a hash leaves our system. It costs nothing, it is checkable with the standard open-sourceots tool, and it proves the one thing a chain is genuinely good at here: that a record existed at a point in time.
RigoAnchor: proof of existence
Every night, all published passport fingerprints are combined into a single Merkle root. That root is submitted to the OpenTimestamps calendar servers, which aggregate submissions from around the world into a Bitcoin transaction. Each passport keeps a short inclusion path proving its own fingerprint sits under that root, so one cheap Bitcoin timestamp covers every passport in the run.
# The Merkle inclusion path for a passport, and the root it proves curl -s https://agririgo.com/api/v1/trace/ZM-COF-2526-DEMO/inclusion # Recompute the root yourself: start from the fingerprint, then for each step # concatenate the sibling on the given side and SHA-256 the pair. # The result must equal merkle_root.
A freshly anchored proof reports bitcoin_confirmed: false until the aggregated transaction is mined, normally a few hours. We show that state honestly rather than calling a pending commitment confirmed.
RigoPrint: the record fingerprint
Every published passport has a fingerprint: a SHA-256 digest over its substantive fields, taken in a fixed, documented order. We publish both the digest and the exact string it was computed from, so you can reproduce it with any standard tool and confirm the result matches.
# 1. Fetch the canonical string and the digest we publish curl -s https://agririgo.com/api/v1/trace/ZM-COF-2526-DEMO/integrity # 2. Recompute the digest yourself from the canonical string printf '%s' '<paste the canonical value here>' | shasum -a 256 # 3. The two hex strings should be identical.
Photos, story text and hashtags are excluded from the fingerprint on purpose. They change for editorial reasons and would churn the digest without altering the traceability claim itself.
The honest scorecard
The passport you are reading matches the published fingerprint
Recompute the SHA-256 digest from the canonical string we publish. If it matches, the content was not altered between our database and your screen.
Two people scanning the same code see the same record
Both agririgo.com and the independent verify.agririgo.com mirror read the same underlying row, so they cannot silently disagree.
This version of the record existed on the date we claim, and was not backdated
Each night every passport fingerprint is committed to a Merkle root that is submitted to the OpenTimestamps calendars and batched into a Bitcoin transaction. The proof is verifiable against Bitcoin by anyone, without trusting Agririgo. A proof shows as pending for a few hours until the transaction confirms.
The producer's certifications and lab results are genuine
We do not audit them. A counter-signature from a co-op officer or agronomist raises confidence, but it is a second person vouching, not a laboratory or an accredited certification body.
Availability is part of integrity
A record you cannot reach when you need it has failed, however well it was secured. RigoContinuity is a second lookup service on separate infrastructure under its own subdomain, so a printed QR code stays checkable even when the main site is not.