FarmlyLedger records every step of a food batch so anyone — a shopper or a government inspector — can check where it came from, how far it travelled, and what it cost the planet, without trusting a supermarket label to tell the truth.
At each stop an identified person validates the batch — “yes, I have this exact lot, here, now.” Farmer, courier, shop, auditor.
Between two checkpoints is a journey leg with a distance and a resource cost — energy, packaging, spoilage — not just kilometres.
Every checkpoint is chained to the one before with a SHA-256 fingerprint. Change any past step and the chain visibly breaks.
One checkpoint = a person tag · a location tag · the batch/cradle tag, scanned in sequence. Whoever scans is the identified witness.
The original food-miles idea argued that local food was inherently better because it travelled fewer kilometres. Life-cycle assessment (LCA) revealed a nuance: transport is typically only 5–10% of a food’s carbon emissions, while production — fertiliser, heated greenhouses, land use — accounts for the vast majority. So the debate has re-framed itself through three lenses:
Geopolitical shocks and climate disruption exposed long international chains as fragile. Localised, 15-minute-city production reduces reliance on complex logistics.
Shorter chains cut cold-chain energy and spoilage in transit, improving nutrient retention at the point of purchase.
“Sustainable” or “locally sourced” is no longer enough. Regulators and consumers want granular data: exact origin, harvest timestamp, carbon intensity.
That’s why FarmlyLedger scores a resource-consumption factor (energy, packaging, losses) — food-miles is the simplified indicator, while the real engine targets the GLEC / ISO 14083 logistics-emissions standards.
Enterprise distributed-ledger platforms — IBM Food Trust on Hyperledger Fabric, SAP and similar networks — were built to solve B2B supply-chain friction and recall risk. They’re excellent at rapid outbreak tracing, GS1/EPCIS interoperability and immutable audit logs. But they’re walled gardens priced for Fortune-500 retailers, they suffer “garbage in, garbage out” (immutability proves data wasn’t edited, not that it was true at entry), and their consumer-facing QR codes usually lead to marketing pages, not raw verifiable provenance.
| Feature | Enterprise DLT (e.g. IBM Food Trust) | Citizen-centric (FarmlyLedger) |
|---|---|---|
| Primary target | Retailers, corporate chains, regulators | Consumers, urban citizens, local producers |
| Data governance | Permissioned / consortium-controlled | Open-source, decentralized, self-hostable |
| Primary goal | Risk mitigation, recall speed, compliance | Proof of origin, micro-food-miles, trust |
| Barrier to entry | High (expensive integration) | Low (open protocols, GS1 Digital Link) |
| Environmental focus | High-level Scope 3 estimates | Granular water/energy per harvest |
Democratized proof of origin (anti-fraud). Mislabelling — imported sold as “local”, conventional as “organic” — exploits consumers. Immutable, witnessed provenance gives direct verification of harvest dates, exact farm coordinates and pesticide history.
Frictionless access. Nobody downloads a crypto app to check an apple. The GS1 Digital Link standard turns an ordinary QR, scanned with a basic phone camera, into a web passport showing provenance, carbon and recall status — no app.
Urban food resilience. Seeing origin gives citizens visibility into their local food sheds — which farms actually feed a neighbourhood — building community trust and local economic circularity.
Regulators have shifted from encouraging voluntary transparency to enforcing mandatory digital traceability.
| Region | Key mandates |
|---|---|
| European Union | Digital Product Passport (DPP) under ESPR; EUDR (GPS plot coordinates proving zero deforestation); CSRD & CSDDD Scope-3 accounting. |
| United States | FDA FSMA Rule 204 — traceability milestone reached in 2026; electronic Critical Tracking Events & Key Data Elements. USDA stricter “Product of USA” origin labelling. |
| Asia-Pacific | Australia — National Agricultural Traceability Strategy. China — state-backed food-safety & cold-chain traceability. |
Each macro finding turned into a concrete design decision:
| Macro finding | FarmlyLedger response |
|---|---|
| Production dominates emissions, not transport (LCA nuance) | Score a resource-consumption factor (energy, packaging, losses); food-miles is the simplified indicator. Targets GLEC / ISO 14083. |
| Enterprise DLT = walled gardens, Fortune-500 focus | Self-hosted, open-standards, low barrier — explicitly anti-consolidation: trust for independent farmers, not power for giants. |
| GIGO — immutability ≠ accurate input | Triplet witness capture (person · location · cradle): an identified human attests at source; the hash chain secures against later edits. |
| B2B focus; retail QR → marketing pages | A public, read-only passport exposes raw, verifiable provenance — “verify it yourself” — for shoppers and governments. |
| Regulation: DPP, EUDR, CSRD, FSMA 204 | EPCIS 2.0 events; per-plot origin; DPP / EUDR export planned; checkpoint events align with CTEs / KDEs. |
| Grassroots: OFN, PGS, Solawi/CSA, OriginTrail | Same ethos: decentralized witnesses echo PGS peer trust; interop via GS1/EPCIS; a Hyperledger Fabric seam if a real consortium forms. |
In one line: the market moved to where FarmlyLedger always pointed — open, standardized, citizen-accessible traceability — delivered with a tamper-evident trust ledger, witnessed triplet capture, and LCA-aware scoring, on infrastructure a local farmer can actually afford.
Background sourced from the FarmlyLedger “Food Miles & Background” project umbrella. Product of Farmlyplace GmbH; developed by protagx.
FarmlyLedger