Every handoff accounted for
Each robot signs what it received and from which robot, even while offline, and catches up when it reconnects.
For warehouse, delivery and drone operators, and their insurers
When an item goes missing between robots, know which robot, and whose.
Robots from different vendors increasingly hand items to each other with no person watching. When an item goes missing or a machine causes damage, the operator needs to know which robot was responsible, and whose robot it was.
What it costs you today
Losses between machines get written off, because nobody can reconstruct which robot held the item and each vendor's logs only show its own side. As robots from different vendors and operators work together, that gets worse, and so does the question of who pays whom for the work done.
What changes
Pay only for proven work
Payment between operators is tied to signed handoffs, so a robot is paid for work it can prove it did.
Evidence after an incident
Operators and insurers see which robot did what, and whether its logs are intact.
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.
Countersign robot handoffs
Send each robot's handoffs and get signed receipts back, by hand or through the API.
$0.02 per receipt
Do it nowTimestamp robot logs
Anchor action logs and sensor files on the public ledger.
$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 |
|---|---|---|
| robot.handoff/1 | the receiving robot | received this item from that robot at this time |
| robot.payment/1 | the paying robot | a payment bound to exactly one handoff |
| robot.action/1 | the robot | performed this task at this time, with a fingerprint of the sensor evidence |
| robot.part/1 | the installer | this serialised part went into this robot |
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. Its building blocks are proven in our space work: custody across thousands of intermittently connected nodes, fleet key management at 4,000+ nodes, and a payment bound to every custody hop on a BSV test chain.
- For insurers. Robot operators and their insurers get evidence nobody has altered after an incident: which robot held the item, what it did, and whether its logs are intact.
- Scope. We record what happened; we do not control the robot or its safety functions.
- 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