Every party its own system, every party its own clock
TMS, terminal system, the recipient's ERP: all with their own time, all changeable by their own administrator.
VIDIMUS/CASE FILES/TRANSPORT, PORT & LOGISTICS
A load delivered, a container through the gate, a parcel signed for — and weeks later the dispute: too late, damaged, never arrived. Every link in the chain keeps its own history. This page shows how you create one shared proof layer where carrier, terminal and recipient see the same facts.
Gate-in 09:41 (UTC+2), container at the terminal. The recipient claims: arrived after the cut-off, extra costs. The terminal's history says 09:41 (UTC+2), the carrier's 09:38 (UTC+2), the recipient has an email from 10:15 (UTC+2). Three systems, three clocks — and the costs are split according to who shouts loudest.
TMS, terminal system, the recipient's ERP: all with their own time, all changeable by their own administrator.
Under the CMR, whoever makes no reservation at delivery largely loses their position — but whoever does make one must also be able to prove it.
In a claim months later, nobody can still reconstruct exactly what happened when. Whoever is best documented wins.
Until proven otherwise, the consignment note is proof of the contract and of receipt. Without a reservation at delivery, the goods are presumed to have been delivered as described; report visible damage immediately, hidden damage within 7 days. Even a suspected "too late" requires a written reservation within 21 days.
Between businesses, evidence is free: scans, system histories and photos are admissible and are weighed. A record in which none of the parties can change anything unnoticed is stronger.
General information, not legal advice. Vidimus supplies evidence; how much weight it carries is for the court to assess — and that weight is exactly what anchoring increases.
Eight disputed deliveries a year × 6 hours × €75, plus an average of €7,500 in shared costs per dispute ≈ €3,600 in hours and €60,000 in costs that you "absorb" for lack of proof. One shared proof layer makes most disputes unnecessary before they even start.
Fictional example: driver Tom Peeters scans at 09:41:03 (UTC+2) at Kaai 1742. On the left what is created technically, on the right what it means in plain language. The fingerprint and the Merkle root really were calculated on this record.
Your gate system already records this today. The problem is not the record, but that it lives in one system that can be changed afterwards.
Unique to exactly this record, and you cannot reconstruct the record from it. Change one character — 09:41:03 (UTC+2) becomes 09:41:04 (UTC+2) — and the whole fingerprint is different. That is how you see later whether anything was changed.
Only whoever holds the key can sign like this; anyone can check that it was them. That establishes who submitted the scan.
Not our clock and not yours. Within five minutes, an external timestamping service stamps it; for customer organisations, GLOBALTRUST, a qualified trust service provider on the EU trusted list, also puts a timestamp on the group, usually within six hours. Neither of them has anything to gain from it. Adjusting a time afterwards therefore stands out.
All scans of those minutes are combined into one root fingerprint; it receives the timestamps of step 04 and goes into Bitcoin via OpenTimestamps, a public register in which a change stands out for anyone who checks, even if we were to try. Each individual scan can still be shown, through its place in the stack.
Every original is stored encrypted, in storage that does not allow deletion or overwriting until the end of the retention period, not even at our request. If it has to go after that, or for privacy reasons, the content key is destroyed: the file is unreadable for good, while the fingerprint still proves that something was there.
The counterparty, the auditor or the court does not have to believe us: with standard software, they check that this scan existed at that moment, submitted by gate-01, and has not been changed since.
Person, company, registration plate and container number are made up. The SHA-256 and the Merkle root really were calculated on the record shown; signature, timestamp and tx id are illustrative values.
No. Anchoring only your own records already strengthens your position: your records are then the only ones for which it can be checked that they have been unchanged since anchoring. If partners take part, everyone looks at the same facts.
Yes — via API or webhook we forward a copy of every event; nothing in your system changes.
Anchoring complements the (e-)CMR: the consignment note remains the contractual document; we make the records around it — scans, times, photos, reservations — recomputable for every party.
You create your account in two minutes, no payment details needed. A director identifies your company once with the Belgian eID; then you create your first logbook in a few minutes. The first 100 records a month and the first measurement source are free. After that, you pay per record or per measurement source, with a minimum of €19 a month.