⛓ Blockchain and Crypto for Honey Traceability

About this simulation

As a honey batch moves from apiary to harvest to extraction to bottling to retail, each hand-off can be written into a block — a record hashed together with the block before it. That hash link is the entire trick behind blockchain traceability: change any earlier record and every hash after it stops matching, which is exactly what a tampered link looks like here.

How it works

• A honey jar batch travels along the chain, triggering each block to compute and display a short hash as it "confirms" the hand-off.
• If a block is tampered, its hash turns red and every block after it in the chain shows a broken link — because each block's hash depends on the one before it.
• Consumer QR scan mode sweeps a scanner over the jar and reports whether the chain the jar is carrying is fully verified or broken, echoing how a shopper's phone scan would behave.
• Loyalty token rewards mint a small glowing token each time a batch completes the chain cleanly — a stand-in for the crypto loyalty programs some honey brands pilot.

Controls

• Chain length — how many hand-off stages the ledger tracks (4–9).
• Batch flow speed — how fast batches move through the chain.
• Tamper at block — pick a block to corrupt its record and watch the break propagate.
• Consumer QR scan mode — toggles a scan-line sweep with a pass/fail verdict.
• Loyalty token rewards — toggles token minting on a clean chain completion.
• ↺ Reset chain — rebuilds the whole ledger. Drag to rotate, scroll to zoom.

Why it matters

Blockchain only guarantees that records weren't altered after they were written — it can't verify that the honey in the jar actually matches the first entry. Garbage in, immutable garbage out. That's why most working honey-traceability systems pair a simple QR-coded batch log with real testing, rather than reaching for a full token economy.