Logs that hold up
Each log segment is fingerprinted and signed by the vehicle as it is written, with a record of any time the logger was offline.
For fleet operators, carmakers and auto insurers
After a crash, have logs nobody can argue with.
When a vehicle with driver assistance or automation is involved in a crash, liability can land on the driver, the fleet, the software supplier or the carmaker. The party that can prove what the vehicle recorded, and which software it ran, wins the argument.
The crash log vehicles and batteries
The vehicle fingerprints each log segment as it writes it, and signs a gap record for any time the logger was offline. Nobody has to take anyone's word that the logs are unchanged.
What it costs you today
Incident data is routinely disputed: was it complete, was it edited, which software version was installed at the time? For fleets and insurers that doubt becomes litigation cost and larger settlements. Carmakers also have to evidence every over-the-air update to regulators, across fleets that are offline much of the time.
What changes
Know exactly what software ran
Every update the vehicle received and installed is signed, so the version in use at any moment is provable.
Settle liability faster
Insurers and fleets start from the same evidence instead of competing expert reports.
Do it now
No call needed. Sign and check free in your browser, or run a paid service on the spot. For a paid service you see the price first and are charged only when the result is delivered; the signed result is yours to download and check.
Sign and check in your browser
Issue update campaigns, sign installs and log segments as a vehicle, and check what was running at an incident.
Free. Keys and files stay on your device.
Open the appIncident evidence package
Which software was running, every log segment around the incident and whether the logs are intact, signed, for an insurer or a court.
$50 per incident
Do it nowUpdate campaign compliance report
Which targeted vehicles have proven the install by their own signature, and which have not.
$10 per report
Do it nowTimestamp incident logs and software records
Anchor log files and update records the moment you have them, so nobody can claim later that they were altered.
$0.10 per file
Do it nowAlready have a BSVKey result file? Check that it is genuine, no account needed.
How it works now vehicles and batteries
Free in your browser: the carmaker signs the campaign, each vehicle signs what it installed and every log segment with its own key, and anyone can check what was running at an incident. A paid package signs it for an insurer or a court.
How it works
Each party signs a small record at the moment it takes responsibility. The records chain together, so a missing, edited or forged one is caught.
| Record | Signed by | Says |
|---|---|---|
| vehicle.update/1 | the vehicle | received update X, verified it, installed it at time T, and the previous version |
| vehicle.log/1 | the vehicle | a fingerprint of each log segment, with gap records for any time the logger was offline |
| battery.handoff/1 | each company in the battery's life | received this battery or material batch, with these documents |
All records use canonical JSON, a SHA-256 fingerprint and an Ed25519 signature, the same primitives proven in our space custody work.
A real run
Update campaign 4.1.3 -> 4.2.0, signed by the carmaker, 8 vans targeted
installed, proven by each van's own signature 6
(one van out of coverage reported 3 days late, from records signed at install)
failed and rolled back 1
no report yet 1
Collision: van-03
records and log files verified: PASS (38 records, chain unbroken)
software running at the time: 4.2.0
logger offline 4 min, restart: signed by the van, not hidden
Tampering:
log segment covering the collision deleted caught
that segment's bytes edited caught
install date moved to after the collision caught
records re-signed with another van's key caught
van reports an image the carmaker never issued caught
campaign forged by someone else caught
Battery pack, cell maker -> pack assembler -> carmaker -> fleet -> recycler: PASS
a forged fleet record (state of health changed) caught
Each van keeps one signed chain of everything it records, so a missing or rewritten entry breaks the chain, whoever tries it.
Where it stands
- Status. Working today, free: sign your own records and check them in your browser with the sign-and-check app, built from the open-source code (Apache-2.0) with automated tests. The onboard signer is small enough for embedded hardware (about 11 KB of code on an ARM Cortex-M4). A design partner helps us connect it to your own systems and devices.
- For insurers. Auto and fleet insurers get incident data nobody has altered and proof of which software was installed when, where liability can shift between driver, operator and manufacturer.
- Scope. We would start with one narrow use, such as update evidence for a fleet operator, rather than a platform.
- Billing. Pay as you go in US dollars or Bitcoin BSV, with prepaid credits or by invoice. Paying in dollars needs no cryptocurrency (how billing works, start now).
Try it on one loss
Send us the records from one loss that went wrong. We will show you what the evidence says.
Email embryospace@gmail.com