may 8 - amazon prime air pushed into metro atlanta. it's the same airspace where walmart-via-zipline + alphabet's wing are already operating. three commercial drone delivery fleets, one urban airspace.
that's the moment proof-of-presence stops being theory.
the new liability question
a package was supposed to land at 1234 oak street. it landed at 1232 oak street, on the porch next door. the customer called support. the dispatcher pulled the drone's gps log. the gps log was generated by the drone itself, on the drone's own clock, signed by the drone's own (or no) key.
in a small-claims case, that log is hearsay. the operator has incentive to massage timestamps. the regulator (faa, dot, state aviation authority) is going to ask for tamper-evidence.
what gridstamp does on-device
- captures gps coordinates at delivery moment
- timestamps via gnss + ntp consensus
- signs the bundle with the drone's hardware key
- emits a hash-chained log to an off-device witness
result - a court-defensible delivery proof that survives a hostile cross-examination.
the integration
import { gridstamp } from '@gridstamp/sdk';
await gridstamp.proveDelivery({
package_id, gps, ts,
drone_signature, witness_endpoint
});
four fields. one signed bundle. fits in 4kb.
why this matters this quarter
faa part 108 (bvlos final rule) is in the docket. proof-of-presence will be a regulatory requirement before it's a competitive feature. the operators that have it shipped early win contracts. the ones that don't argue about gps logs in small-claims for the rest of the year.