Verification & Blockchain
Understand RivetChain's 3-tier verification system, blockchain anchoring, and how QR codes connect physical products to their digital records.
How Verification Works
RivetChain uses a three-tier verification system to ensure the integrity and authenticity of every product record. When a product is verified, each tier is checked independently and the results are combined into a single verification report. This layered approach means that even if one system were compromised, the other tiers would detect the discrepancy.
Tier 1: Database Integrity
Every event is hashed with SHA-256 when it is created. The hash covers the event's full contents (its payload) and its unique identifiers, so any later change to the record produces a different hash. During verification, RivetChain recalculates these hashes and compares them to the stored values. If any record has been altered after creation, the hash comparison will fail and the verification report will flag the inconsistency.
This tier runs entirely within the RivetChain database and provides near-instant results. It catches any tampering that may have occurred at the application or database level.
Tier 2: Blockchain Proof
For products where anchoring is turned on (it is off by default),RivetChain anchors event hashes to the Solana blockchain to create an external, tamper-proof timestamp. Rather than writing every individual event to the blockchain (which would be prohibitively expensive), events are grouped into batches. Each batch is processed into a Merkle tree, and the root hash of that tree is written to a Solana transaction.
During verification, RivetChain reconstructs the Merkle proof for the specific event being checked and verifies it against the on-chain root hash. This proves that the data existed at the time the blockchain transaction was confirmed and has not been modified since. The Solana blockchain provides finality within seconds, and the transaction can be independently verified by anyone using a block explorer.
Tier 3: IPFS Payload
For every anchored batch we also publish a batch record to IPFS (InterPlanetary File System) via Tatum, listing each event's hash, type and timestamp — not the event contents. IPFS stores content by its cryptographic hash, so the address itself is a proof of the content. The IPFS address is written into the Solana transaction, so anyone can check that the published batch record is the one that was anchored.
This is an independent public copy of the proof, not a backup of your data: product details stay in the RivetChain database.
Batch Anchoring Process
Understanding the batch anchoring process helps explain why verification is structured the way it is. Here is how events flow from creation to full blockchain verification:
- 1
Event creation
When you add an event to a product (such as a status change, transfer, or file upload), it is saved to the database immediately with a cryptographic hash. The product is usable and Tier 1 verifiable right away.
- 2
Batch collection
Once an hour, a background job collects the unanchored events of products with blockchain anchoring turned on into a new batch. The events are organized into a Merkle tree, which compresses all of their hashes into a single root hash.
- 3
IPFS upload
A batch record listing each event's hash, type and timestamp (not the event contents) is published to IPFS. Its content address (CID) is kept with the batch.
- 4
Blockchain transaction
The Merkle root and the IPFS address are written to the Solana blockchain in a single transaction. Once the transaction is confirmed, the batch is marked as anchored and the transaction ID is stored, completing the three-tier chain of evidence.
Public Verification Page
Every product registered on RivetChain has a unique public verification page accessible at /verify/:productId. This page does not require authentication and is designed for end consumers, auditors, or anyone who wants to confirm a product's authenticity. The page displays the product's event history along with the verification status of each tier.
You can share the verification page URL directly, or embed it in your own website using the RivetChain verification widget. The widget provides a compact, brandable verification interface that loads directly on your product pages.
QR Codes on Certificates
When you generate a certificate for a product, RivetChain automatically includes a QR code that links to the public verification page. Scanning the QR code with any smartphone camera opens the verification page in a browser, allowing instant verification without needing to type a URL or search for the product manually.
This is particularly useful for physical products: you can print the certificate or attach the QR code to packaging, tags, or documentation. Anyone in the supply chain or the end consumer can scan and verify authenticity on the spot.