세 개의 드론 함대, 하나의 공역, proof-of-presence 없음

Source: Dev.to

Three Drone Fleets, One Airspace

May 8 – Amazon Prime Air was pushed into Metro Atlanta, joining the same airspace where Walmart‑via‑Zipline and Alphabet’s Wing are already operating. Three commercial drone‑delivery fleets are now sharing a single urban airspace.

Proof‑of‑Presence Becomes Reality

A package was supposed to land at 1234 Oak Street but ended up on the porch next door at 1232 Oak Street. The customer called support, and the dispatcher pulled the drone’s GPS log. That log was generated by the drone itself, using the drone’s own clock and signed with the drone’s hardware key (or no key at all).

In a small‑claims case, such a log is considered hearsay because the operator could manipulate timestamps. Regulators (FAA, DOT, state aviation authorities) will therefore require tamper‑evidence.

Desired Properties

• Capture GPS coordinates at the exact delivery moment.
• Timestamp using GNSS + NTP consensus.
• Sign the data bundle with the drone’s hardware key.
• Emit a hash‑chained log to an off‑device witness.

Result: A court‑defensible delivery proof that survives hostile cross‑examination.

Technical Implementation

import { gridstamp } from '@gridstamp/sdk';

await gridstamp.proveDelivery({
  package_id,
  gps,
  ts,
  drone_signature,
  witness_endpoint
});

• Four fields (package ID, GPS, timestamp, drone signature).
• One signed bundle that fits within ~4 KB.

Regulatory Outlook

FAA Part 108 (BVLOS final rule) is currently in the docket. Proof‑of‑presence will soon become a regulatory requirement before it can be used as a competitive feature. Operators that ship this capability early will win contracts, while those that do not may spend the rest of the year arguing about GPS logs in small‑claims courts.