Preuve de traçabilité
Bloc cryptographique attaché à une donnée de traçabilité : empreinte du contenu, signature Ed25519 de l'émetteur, et le cas échéant la référence de l'ancrage. Il permet de rejouer la vérification sans faire confiance à celui qui présente la donnée.
Was der Blog dazu sagt
- Le nœud ne dit rien tout seul
Cinq siècles après, on sait encore lire les nombres inscrits dans les khipus incas — mais plus ce qu’ils comptaient. Ce que cette asymétrie dit de nos sauvegardes, de nos énumérations et de la différence entre zéro et rien.
- Structuring your lot numbering: the foundation that makes everything else possible
A badly designed lot number breaks traceability before the first scan. What an identifier must encode, the pitfalls of numbering by date alone, and how to migrate without losing the history.
- Upstream and downstream traceability: the difference explained simply
Upstream, downstream, internal: the three notions most often confused by an operator discovering the regulation, with concrete examples for each and what “one-up, one-down” really means.
- Choosing food traceability software: the criteria that matter
Spreadsheet, ERP, dedicated solution: what really separates traceability tools, the questions to ask before signing, and the signs that a tool will not hold up on the day of an inspection or a recall.
- EUDR for timber: the special case of a long traceability chain
Log, sawn timber, panel, furniture: timber goes through more processing stages than the other EUDR commodities before reaching the European market. How due diligence is passed from one link to the next without getting lost.
- Diversifying your outlets: selling both through short supply chains and to a retailer
Direct selling and the large-retail market follow different logics, not incompatible ones. How to split your production, what changes between the two, and the pitfalls of poorly calibrated diversification.
- Choosing a traceability solution: SaaS, bespoke or spreadsheet — the criteria
Three families of solutions, three very different cost structures. How to estimate the real cost of each over three years, not just the entry price, and when a bespoke investment finally makes sense.
- Traceability APIs: what to ask a software vendor before you sign
Call rate, export format, guaranteed availability, reversibility: the technical questions a non-developer can ask to assess a traceability API without getting locked into a tool.
- Migrating from paper traceability to a digital tool: the method
Don’t switch everything over at once, keep paper as a safety net during the transition, and know where to start so you don’t burn out in the first month. The method for digitising traceability without a break.
- Integrating your till or ERP with a traceability tool: the integration pitfalls
Two systems that do not speak the same identifier language, a synchronisation that fails silently, double entry that persists despite the integration — the most frequent pitfalls, and how to avoid them before you sign.
Wo es umgesetzt ist
lib/dfc/export.tslib/onchain-anchor.ts