PNTMAP capability status

• ADS-B-derived integrity anomaly monitoring: Cell-level low-NIC proportions are computed continuously from node telemetry and published on the map and stats surfaces.
• ML-DSA telemetry signing: ML-DSA-65 (FIPS 204) signatures are generated at each sensor and verified at ingest before storage. This covers origin and integrity at ingest only.
• Independent evidence anchoring: Live. Each ledger block header is independently timestamped via two unrelated mechanisms: the Bitcoin blockchain (OpenTimestamps) and an RFC 3161 timestamp authority (DigiCert). First confirmed Bitcoin attestation: ledger block 55 → Bitcoin block 962625 (2026-08-15 21:00:27 UTC), externally verified against two independent block explorers; RFC 3161 timestamps verified against DigiCert's root CA. Recent blocks are anchored on the next scheduled run.
• Per-node signed ingest commitments (completeness): Each node publishes a daily ML-DSA-65 (FIPS 204)-signed commitment to its ingest chain, independently anchored via OpenTimestamps (Bitcoin).
• Phase 1 nodes (2 of 20 live): Coverage is exactly the reception footprint of the live nodes. Absence of a record outside that footprint carries no information.

Publicly broadcast ADS-B integrity fields (NIC, NACp, SIL, ADS-B version) received by PNTMAP-operated ground nodes on UK territory. 2 of 20 planned Phase 1 nodes are live. No third-party interference feed is republished, and no GNSS-band RF measurement contributes to any published figure.

A node is reported offline when its last accepted report is older than 10 minutes. The same threshold applies on every public surface.

• Jamming indicators: derived indirectly from ADS-B integrity degradation. The platform publishes indicators, not confirmed jamming.
• Spoofing indicators: only the graded evidence classes described in the methodology are published. No confirmed spoofing determination has been made from platform data.
• Direct RF detection: not live. No node measures the GNSS bands today, so no anomaly on the platform is RF-corroborated.
• Controlled validation: not carried out. No controlled jamming or spoofing trial has been run against the network.

• Direct RF sensing and corroboration (No live RF node): No node measures the GNSS bands today, so no ADS-B anomaly on the platform is RF-corroborated.
• Automatic event lifecycle (Not live; operator-curated): Sustained anomalies are submitted for operator review. Opening, revision and closure of event records are manual.
• Commercial API SLA and pricing (Not yet published): Latency and availability targets, commercial model and pricing are not published. Access is arranged case by case.
• Classified deployment (Separate scoped engagement, not the public platform): The public platform operates at OFFICIAL and holds no classified-handling accreditation. Requirements above OFFICIAL are an individually scoped engagement.

• Coverage is exactly the reception footprint of the live nodes. Absence of a record outside that footprint carries no information.
• Integrity degradation has causes other than interference, including avionics behaviour, receiver configuration and terrain. The platform reports indicators.
• Event opening, revision and closure are operator-curated, not automatic.
• Signature verification covers origin and integrity at ingest only. Anchoring makes subsequent alteration detectable; it does not prove that a record was correct when it was written.

Transport uses TLS 1.3 with hybrid post-quantum key agreement (X25519MLKEM768, ML-KEM / FIPS 203) negotiated by default at the edge and on the backend link, for supporting clients (Chrome/Edge 124+, Firefox 132+, recent OpenSSL). Older clients fall back gracefully to classical X25519, and certificate authentication remains classical (ECDSA/RSA).

Each ledger block header is independently timestamped via two unrelated mechanisms: the Bitcoin blockchain (OpenTimestamps) and an RFC 3161 timestamp authority (DigiCert). Recent blocks are anchored on the next scheduled run, so the most recent blocks may not carry a Bitcoin attestation yet; hash chaining means one confirmed attestation fixes every block below it.

• Commissioning of RF-capable nodes so that ADS-B anomalies can be corroborated.
• Controlled evaluation against a known, authorised interference source.
• Completion of the Phase 1 node roll-out to 20 nodes.
• Published commercial API service levels.

Acceptance criteria and sequencing are on the validation status and test roadmap.

Capability record last updated 2026-08-15. Detection methodology v1.0, published 2026-08-14.

Machine-readable mirror: /capability-status.json. Related pages: GNSS interference detection methodology, validation status and test roadmap and verify cryptographic event evidence.