xNuke: Nuclear Facility Monitoring
XorIDA splits nuclear sensor readings across independent international agencies, guaranteeing no single agency can falsify safety data or suppress critical alerts.
The Problem
Nuclear sensor data integrity relies on trust in single monitoring agencies. A compromised or politically pressured agency can suppress safety alerts, falsify readings, or delay critical warnings.
The International Atomic Energy Agency (IAEA) and national regulators depend on sensor networks that report through single organizational channels. Reactor temperature, radiation levels, coolant flow rates, and containment pressure readings all pass through a single chain of custody before reaching decision-makers.
This architecture has a fundamental weakness: a compromised monitoring agency — whether through state pressure, insider threat, or cyberattack — can alter readings to mask dangerous conditions. The Fukushima and Chernobyl incidents demonstrated that institutional trust in monitoring data is insufficient when lives are at stake.
The Old Way
The PRIVATE.ME Solution
XorIDA splits every sensor reading across independent international agencies. Threshold reconstruction guarantees that no single agency — regardless of political pressure — can fabricate a valid reading.
Each sensor reading is split into N shares using XorIDA threshold sharing. Shares are distributed to independent, geographically diverse agencies — IAEA, national regulators, and independent watchdogs. Any K of N shares reconstruct the original reading. Fewer than K shares reveal nothing.
To falsify a reading, an adversary would need to simultaneously compromise K independent agencies across multiple jurisdictions — a vastly harder attack than compromising a single organization. Every share carries HMAC-SHA256 integrity verification, making even single-bit tampering detectable.
The New Way
How It Works
A four-stage pipeline: sensor ingestion, XorIDA split with typed integrity metadata, multi-agency distribution, and HMAC-verified threshold reconstruction.
Tamper evidence: Every share carries HMAC-SHA256. Altered readings fail verification immediately, triggering typed TAMPER_DETECTED alerts to all participating agencies.
Fail-safe availability: If N-K agencies go offline, the system still produces verified readings from the remaining K agencies.
Use Cases
Split inspection sensor data across IAEA, host country regulator, and independent observer. No single party can suppress findings. Threshold reconstruction requires multinational cooperation.
Treaty ComplianceContinuous reactor temperature, pressure, and coolant flow readings split across independent safety organizations. Anomalies detected even if one monitoring body is compromised.
Real-Time MonitoringEnvironmental radiation sensors around nuclear facilities report through split channels. Communities, regulators, and operators each hold shares — no single party controls the narrative.
Environmental SafetyArms control treaty verification data split across signatory nations. Each nation holds shares; treaty compliance is verifiable only through multinational threshold cooperation.
Arms ControlIntegration
import { splitReading, verifyIntegrity } from '@private.me/xnuke'; // Split sensor reading across 3 agencies (2-of-3) const shares = await splitReading( sensorReading, ['iaea', 'national-regulator', 'independent-watchdog'], { n: 3, k: 2 } ); // Verify integrity at reconstruction point const result = await verifyIntegrity(collectedShares); if (result.ok) { // result.value contains the verified sensor reading processReading(result.value); }
Security Properties
| Property | Mechanism | Guarantee |
|---|---|---|
| Confidentiality | XorIDA K-of-N threshold | Information-theoretic (unconditional) |
| Integrity | HMAC-SHA256 per share | Tamper detection before reconstruction |
| Non-Falsification | Multi-agency threshold | Requires K compromised agencies |
| Availability | N-K redundancy | Tolerates N-K agency failures |
| Accountability | Typed integrity alerts | Tamper traced to specific agency |
Verifiable Data Protection
Every operation in this ACI produces a verifiable audit trail via xProve. HMAC-chained integrity proofs let auditors confirm that data was split, stored, and reconstructed correctly — without accessing the data itself.
Read the xProve white paper →
Ready to deploy xNuke?
Talk to Ren, our AI sales engineer, or book a live demo with our team.
Ship Proofs, Not Source
xNuke generates cryptographic proofs of correct execution without exposing proprietary algorithms. Verify integrity using zero-knowledge proofs — no source code required.
- Tier 1 HMAC (~0.7KB)
- Tier 2 Commit-Reveal (~0.5KB)
- Tier 3 IT-MAC (~0.3KB)
- Tier 4 KKW ZK (~0.4KB)
Use Cases
Deployment Options
SaaS Recommended
Fully managed infrastructure. Call our REST API, we handle scaling, updates, and operations.
- Zero infrastructure setup
- Automatic updates
- 99.9% uptime SLA
- Enterprise SLA available
SDK Integration
Embed directly in your application. Runs in your codebase with full programmatic control.
npm install @private.me/xnuke- TypeScript/JavaScript SDK
- Full source access
- Enterprise support available
On-Premise Upon Request
Enterprise CLI for compliance, air-gap, or data residency requirements.
- Complete data sovereignty
- Air-gap capable deployment
- Custom SLA + dedicated support
- Professional services included
Enterprise On-Premise Deployment
While xNuke is primarily delivered as SaaS or SDK, we build dedicated on-premise infrastructure for customers with:
- Regulatory mandates — HIPAA, SOX, FedRAMP, CMMC requiring self-hosted processing
- Air-gapped environments — SCIF, classified networks, offline operations
- Data residency requirements — EU GDPR, China data laws, government mandates
- Custom integration needs — Embed in proprietary platforms, specialized workflows
Includes: Enterprise CLI, Docker/Kubernetes orchestration, RBAC, audit logging, and dedicated support.