Try a real one: a911854afe86dfbab901…
Every farm action recorded on Teivaka Agriculture Ecosystem — eggs collected, vaccinations given, feed delivered, sales logged — is written as an immutable, hash-chained audit event. Each event row carries a SHA256 hash that links to its predecessor, forming a tamper-evident chain.
Bank Evidence PDFs generated by Teivaka include a verification URL and QR code. Anyone holding the document can verify, in real time, that the audit chain has not been altered since the document was generated.
This QR code links to a real audit event in our chain. Scan with your phone to see what a successful verification looks like.
a911854afe86dfbab901a4e81460a21a1f781ca1df0fb0adebcb4d0c9f78342f
Or visit: /verify/a911854afe86dfba…
Each audit event in the chain stores:
To alter any historical event, an attacker would need to recompute every subsequent hash for that farm. At every verification request each of the farm's records is re-checked against what was saved — its content, its own hash and its link to the one before — so a changed or missing record shows.
Verification today confirms three things about a record: that it exists in the registry, that its hash chain is intact end-to-end, and when and what type of event it was. The math is SHA256 hash-chaining — any party may re-implement the check.
The full Trust Architecture — trust dimensions (identity, evidence, attestation, behavioural, resilience) and verification levels L0–L5 — is being rolled out progressively. This page will show those scores only when they are computed from real evidence and attestations, never as decoration.
The verification protocol does not require a Teivaka account. The math is open. The data is the farmer's. The protocol remains usable indefinitely, including after any change of control of Teivaka PTE LTD, per Covenant §9.
Verification responses include only: the record type, its time, a farm identifier, whether that record and the farm's records re-check against what was saved, whether the record's details are sealed in it, and counts of records. They never include farmer names, contact details, location data, what a record says, internal identifiers, or any business-sensitive information. The verification surface is designed for trust, not for data extraction.