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.
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: open the service, see the price, and run it on the spot. You are charged only when the result is delivered, and the signed result is yours to download and check.
Timestamp 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
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.
Where it stands
- Status. In design, looking for a design partner. The onboard signer is already small enough for embedded hardware (about 11 KB of code on an ARM Cortex-M4).
- 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 BSV, with prepaid credits or by invoice. Paying in dollars needs no cryptocurrency (how billing works, start now).
Become the design partner
We are looking for one company to shape this with. You bring the real handoffs; we build it around them.
Email embryospace@gmail.com