Drone Operators · Step 2
Register a drone
Registration ties a drone gateway to you. You approve its certificate request with your passkey, and the drone's public key is written to Hyperledger Indy as a decentralised identifier that anyone can look up.
1. Create your operator passkey
The console uses passkeys instead of passwords. A passkey lives on this computer, your phone, or a security key, and is what signs your approvals. Use Chrome or Edge.
- Open operator.geonft.eu and choose Register.
- Enter your name and your operator licence number. A name can be registered only once.
- Press Create passkey and complete your platform's prompt.
The console signs you in. Your name and licence number appear at the top of the page. Behind the scenes an operator record urn:ogc:feature:operator:<id> is created; this is the owner that will later appear on your flights' geoNFTs.
Signing in later
Open the console, enter your username, press Sign in, and complete the passkey prompt. A session lasts 12 hours; Sign out ends it sooner. A passkey created for operator.geonft.eu does not work on another address.
2. Wait for the ledger
At the top of the signed-in page a status line says whether the identity ledger is reachable. Enrollment and flights are only possible when it reads:
Ledger <name> is open
If it says Ledger is not open. Enrollment stays unavailable., the services are still starting or the ledger is down. Wait and reload.
3. Enroll the drone gateway
Make sure the gateway is powered and shows esp32s3 gateway ready (see Set up a drone). Then open Drones, card 2. Enroll a drone.
- Set Alias, the name shown in your drone list (default
drone-1). -
Press Start enrollment over USB or Start enrollment over Bluetooth.
- USB: the browser asks for a serial port. Choose the ENROLL adapter (wired to GPIO 43/44). The page opens it at 115200 baud.
- Bluetooth: choose the device named
tcs-esp32.
- Wait until the page shows a CSR fingerprint. The gateway has created its certificate signing request inside the secure element.
- Press Approve enrollment and complete the passkey prompt.
- The page shows the drone's
did:indy:…identifier, and the drone appears under Your drones. Press Select on its row; the Flights page uses the selected drone.
If the gateway was enrolled before, the page says so and the button reads Finish enrollment. The DID does not change, because it is derived from the drone's key; only the alias is updated.
What registration created
- A decentralised identifier on Hyperledger Indy
- The operator service writes the drone's Ed25519 public key to Indy as a NYM. The DID, for example
did:indy:sandbox:4WqN8k…, is derived from that key. Anyone can resolve it athttps://resolver.geonft.eu/1.0/identifiers/<did>. - A link between the identity and the signing key
- The drone signs, with its identity key, an attribute on its own NYM that publishes the P-256 key inside the ATECC608. Every flight token is bound to that key, and the QGIS plugin later checks this link (level L5 of the verification result).
- A drone certificate
- A PKCS#7 certificate is returned to the gateway and stored there.
- An OGC Connected Systems system
- The drone is registered on
cs.geonft.euwith datastreams for position, battery, heading, speed, armed state, and images.
Hand over the alias and the did:indy:… value, so the crew knows which gateway was approved.
If something does not work
| What you see | What to do |
|---|---|
Ledger is not open. | Wait; the services or the ledger are starting. |
| USB or Bluetooth marked unavailable | Switch to Chrome or Edge. |
| No CSR fingerprint appears | On USB, pick the ENROLL adapter, not the flight-controller or GCS adapter. On Bluetooth, stay close to tcs-esp32. Check that the ATECC608 is wired and answering. |
| Approve enrollment does nothing | Run Start enrollment again and wait for the fingerprint line. |