Proof of Flight/Ledger explorer
Concept · Ledger explorerEvery delivery, checkable.
The ledger is where a flight's record becomes evidence. Each batch of decisions is anchored as a Merkle root and co-signed by the operator, the regulator, the insurer and the UAS service supplier. This is what the explorer would look like, and how a customer checks a delivery without taking anyone's word for it.
Latest block
—A new batch every few secondsValidators
4 of 4Operator · Regulator · Insurer · USSRecords anchored today
—Across all operatorsConfirmation
1.6 sAverage over the last hourPublic checkpoint
—Hourly state rootFor customers
Verify a delivery in your browser.
A delivery receipt holds one record, the photo hash and a short Merkle proof. Verification recomputes the record's hash, climbs the proof and compares the result with the root the validators signed. Every hash below is computed live on this page.
Sample receipt for flight DLV-0193, record #0009.
Moves the delivery time in the operator's stored copy by three minutes, the kind of edit a dispute might tempt.
- 1Read the receipt
Record, proof and batch ID
- 2Recompute the record hash
SHA-256 of every field plus the previous hash
- 3Climb the Merkle proof
Combine with the sibling hashes up to a root
- 4Compare with the ledger
The root anchored in the batch's block
- 5Check the signatures
At least 3 of 4 validators
Flight data trail
DLV-0193, from route choice to sealed landing.
The view a regulator or insurer would open: every record, grouped by the batch that anchored it, with the Merkle roots that tie the flight together. Select a record to read it.
Network
Four validators, one shared history.
Each batch root becomes a block, and a block counts once at least three of the four validators sign it. Every hour, the ledger's state root is written to a public chain.
| Validator | Run by | Reads | Last signed | Status |
|---|---|---|---|---|
| Operator nodeWrites batches | Delivery operator | Its own flights, in full | — | Online |
| Regulator nodeSigns and audits | Aviation regulator | Any flight, on request | — | Online |
| Insurer nodeSigns | Fleet insurer | Flights linked to a claim | — | Online |
| USS nodeSigns, checks conformance | UAS service supplier | Tracks and flight intents | — | Online |
A late signer is flagged on the block and its signature is added when it catches up. The block already counts at 3 of 4.
Latest blocks
LiveHow verification works
Five checks, each one independent.
- 01
Hash the record
h9 = SHA-256(record9 ‖ h8)The aircraft hashes every field of the record together with the previous record's hash. Change one character and the hash changes completely.
- 02
Follow the chain
record9.prev = h8Each record names the hash before it, so records can't be dropped, reordered or inserted without breaking the next link.
- 03
Climb the proof
root = H(H(h7‖h8) ‖ H(h9‖h9))A batch combines record hashes pairwise into one root. A receipt only needs the hashes along its path, not the other records.
- 04
Match the block
root = A3 · block 1,204,334The root is anchored as a block that counts once three of four validators sign it. No single party can sign alone.
- 05
Check the checkpoint
state root → public chain, hourlyThe ledger's state root goes to a public chain every hour, so even the full consortium can't rewrite older history.
Access
Who can see what.
Validators can read the whole ledger. The data behind it is disclosed by role, and personal data never leaves the operator.
| Data | Customer | Regulator | Insurer | USS | Public |
|---|---|---|---|---|---|
| Batch roots and block signatures | Yes | Yes | Yes | Yes | Yes |
| Decision summaries | Own delivery | Yes | Claim-linked | Yes | 24 h delay |
| Full decision records | Own delivery record | Yes | Claim-linked | Conformance fields | — |
| Raw telemetry and sensor frames | — | On request | Claim-linked | — | — |
| Delivery photo | Yes | On request | Claim-linked | — | — |
| Model passport | Summary | Full | Full | Summary | Summary |
| Customer name and address | — | — | — | — | — |
Customer name and address stay with the operator and never reach the ledger or its validators.
Proof of Flight
Back to the framework.
Watch the live flight that produced this trail, or request the technical brief.