Record a lot event
Every significant event in a production lot — a transformation, a split, a quality check, a shipment — becomes a proof anyone can verify. Your industrial data stays in your systems: only the proof of the event goes on chain.
Try it in one click
The demo builds a small but real supply chain — steel coil received, cut into blanks, split into two customer lots, one checked and shipped — and records six genuine proofs on the LKSCOIN blockchain. Then follow the genealogy and see which lots a recall would touch, and which it would not.
Or record your own event
Nothing here is mandatory except the lot, the event and who is recording it.
The lot
A GS1 identifier (GTIN + batch or serial) is recognised automatically and gets a resolvable Digital Link; anything else works too.
What happened
Details
This is how confidential detail gets proved without being disclosed: keep the file, publish only its fingerprint, and you can show later that it never changed.
Fill in the lot, the event and the organisation to continue.
The proof of the event, not the event's data
The fields above are canonicalised (JCS, RFC 8785), hashed, and that hash is written to the blockchain inside the same batch as every other proof — so a lot event inherits the block confirmation and the Bitcoin anchoring without costing a separate transaction.
Each event also commits to the one before it on the same lot. The blockchain proof shows when an event was recorded; the chain of hashes shows that the history was not reordered or quietly pruned afterwards.
What stays out: everything you did not type here. Recipes, measurements, supplier prices and personal data belong in your systems. Commit to them with a hash and you can still prove, years later, that the document you hold is the one that existed then.