1. Set up the drone
Wire the ESP32-S3 gateway and its ATECC608 secure element between the flight controller and the ground station, flash the firmware, and install MAVProxy with the tcs module.
Drone Operators · operator.geonft.eu
As an operator you give a drone its identity, open each flight, and close it. The drone signs everything in between. The result is a flight record that customers can verify without trusting you, us, or the server.
Wire the ESP32-S3 gateway and its ATECC608 secure element between the flight controller and the ground station, flash the firmware, and install MAVProxy with the tcs module.
Create your operator passkey, connect the gateway over USB or Bluetooth, and approve its certificate request. The drone receives a did:indy identity.
Open a flight in the console, arm the ground station with tcs arm, fly, then tcs seal and close the flight. The flight is minted as a geoNFT.
tcs module on the ground station| Moment | You do | Evidence created |
|---|---|---|
| Register | Approve the drone's certificate request with your passkey | Drone did:indy on Hyperledger Indy, OGC Connected Systems system |
| Open flight | Sign the flight document with your passkey and hand the pairing code to the ground station | Connected Systems deployment, flight token bound to the drone key |
| During flight | Nothing; the gateway signs, MAVProxy posts | Signed observations, IPFS pictures, Fabric hashes |
| End of flight | Ask for tcs seal, then close the flight with your passkey | Manifest, deployment hash, geoNFT on Fabric |
You do not sell or license flights yourself. Closed flights are reviewed and published by flight analysts in the customer portal.
| Service | Address |
|---|---|
| Operator console | https://operator.geonft.eu |
| Connected Systems API (Swagger) — OGC API – Connected Systems with the Trusted Connected Systems extension | https://cs.geonft.eu/docs |
| Picture gateway | https://ipfs.geonft.eu/ipfs/<cid> |
| Drone DID resolver | https://resolver.geonft.eu/1.0/identifiers/<did> |