Reference

Glossary

The words you meet in the operator console, the portal, the wallet and the QGIS report, explained in one or two sentences each.

Anchor hash
The SHA-256 hash of one accepted observation (its canonical JSON). Connected Systems writes it to the Fabric chaincode assets, so a later change to the observation is detectable.
AnonCreds
The verifiable-credential format used for flight certificates. The wallet can prove it holds a valid certificate without handing over a copy that could be reused.
ATECC608
A hardware secure element on the drone gateway. It creates the drone's P-256 signing key and never lets it out; every observation is signed inside the chip.
Certificate (license)
The credential a consumer holds in the GeoNFT Wallet for one flight. It carries the flight's deploymentId and its policy. The portal calls it a license.
Classified flight
A catalog listing that is not part of the subscription. Customers request access and a flight analyst grants or denies each request.
cnfJkt
The thumbprint of the drone's secure-element key. Flight tokens are bound to it, the manifest fixes it, and the drone publishes the key on its did:indy.
Connected Systems API
The OGC API – Connected Systems service at cs.geonft.eu, with the Trusted Connected Systems extension. It stores drones (systems), flights (deployments), datastreams and observations, and checks every drone signature before storing.
Deployment
One flight in Connected Systems, identified like dep-3fa85f64-…. It is open from Open flight until Close flight, and only accepts observations while open and unsealed.
Deployment hash
The SHA-256 of the flight's canonical manifest. It is the value minted in the geoNFT and recomputed by the QGIS plugin.
did:indy
A decentralised identifier on Hyperledger Indy. Each drone gets one at registration, derived from its Ed25519 public key. Resolve it at resolver.geonft.eu.
DPoP
OAuth 2.0 Demonstrating Proof of Possession. Each observation is posted with a short proof signed by the drone's key, so a stolen flight token is useless without the drone.
Drone chain
The order of observations as signed by the drone: each proof carries a boot id, a counter n and a link prev to the previous one. Missing numbers show gaps that nobody can hide.
Endorsement
A Fabric peer's signature on a transaction. A flight NFT needs Secure Dimensions and at least one of GeoID Works or 4113 Engineering.
Flight analyst
A portal user with the issuer role who publishes flights in the catalog and manages access.
Gateway
The ESP32-S3 board with the ATECC608 between flight controller and ground station. It signs observations; MAVProxy posts them.
geoNFT
The NFT minted on Hyperledger Fabric when a flight closes. It holds the deployment hash, the manifest and the owner (the operator), and is the anchor every verification starts from.
GeoXACML policy
An OGC GeoXACML 3 access-control policy attached to each published flight, for example a geo-fence. It is signed into every certificate and evaluated per observation.
Included flight
A catalog listing covered by the monthly PayPal subscription. Subscribers press Get license.
IPFS
Content-addressed storage for picture bytes. A picture's address (CID) and SHA-256 are stored with its observation; it is served at ipfs.geonft.eu.
Lineage
The per-observation record of a flight: anchor hash, chain value, the drone's signed proof and the seal. The QGIS plugin recomputes everything from it.
Manifest
The summary of a closed flight: drone, key, operator, start and end, close reason, server-chain head, drone-chain segments and seal. Its hash is the deployment hash.
Pairing code
The short code shown when a flight is opened. The ground station uses it with tcs arm to fetch the flight token.
Passkey
A password-less sign-in key kept on your device. Operators sign enrollment, open and close with it; portal users sign in with one.
Seal
The drone's signed statement that its chain ends here, sent by tcs seal. After it the gateway signs nothing more for the flight, and Connected Systems accepts no more observations.
Server chain
A hash chain Connected Systems extends with every stored observation. Its head is fixed in the manifest, so dropping or reordering observations later breaks it.
Trusted Connected Systems
An extension of the OGC API – Connected Systems Standard. It keeps the standard's systems, deployments, datastreams and observations, and adds ledger identities for systems, observations signed by the drone, sealed deployments and ledger anchoring.
tcs module
The MAVProxy module of Trusted Connected Systems. It arms a flight, relays the gateway's signed observations to the API, and seals and disarms.
GeoNFT Wallet
The iPhone app, distributed through TestFlight, that holds flight certificates and answers proof requests from the portal.