Skip to content
Technology How it works Breeder — Hyperion Burner — Aegis Burner — MetroVolt AI-Native Architecture Magnets Fuel cycle Safety Roadmap
Solutions AI & Data Centers Defense & Government Grid & Baseload Neutron Detection Quantum
Learn Technical Library
Proof Publications Whitepapers Technical Library Open Science & Reproducibility The Honest Gates
Company About / Mission Leadership Environment Health & Safety Investors Careers Press Contact
3D Model
AI Architecture › Security & Zero-Trust
Security & Zero-Trust

FPGA Bitstream Encryption and Authentication

Control-loop bitstreams are both encrypted and authenticated, so an attacker can neither read the design nor load a modified one onto a Kronos control FPGA.

STRATEGY / SLOW ▲ ▼ MICROSECOND REAL-TIMEL7Ecosystem & Strategytelemetry ▲ control ▼open ▸L6Experience & Visualizationtelemetry ▲ control ▼open ▸L5Applications & Copilotstelemetry ▲ control ▼open ▸L4Orchestrationtelemetry ▲ control ▼open ▸L3Twin Modeling & AItelemetry ▲ control ▼open ▸L2Data Fabrictelemetry ▲ control ▼open ▸L1Control Planetelemetry ▲ control ▼open ▸L0Foundationtelemetry ▲ control ▼open ▸PHYSICAL S.M.A.R.T. GENERATOR PLANTBREEDER · HYPERION1R0 1.2 m · A 2.5 · 16.84 T · δ −0.30BURNER · TANDEM MIRROR2317 T throat · 26.49 T plug · fₙ 5.44% · DEC1 center stack + plasma · 2 high-field plug · 3 expander → direct converterCOLOR GRAMMAR strategy AI-workflow infra/data models reactor/DECLINE SEMANTICStelemetry (µs)controlKRONOS FUSION ENERGYAI-NATIVE S.M.A.R.T. GENERATORMASTER BLUEPRINTSHEET 01REV. 2026-08L0-L7 · 2 MACHINES
The AI-Native S.M.A.R.T. Generator Master Blueprint — eight layers (L0→L7), one control stack, wired to both machines. Telemetry rises in microseconds; control descends the same path.

Two distinct guarantees

Bitstream security needs two separable properties. Encryption (confidentiality) stops an adversary from reverse-engineering the control design or extracting embedded secrets by reading flash or sniffing the configuration bus. Authentication (integrity) stops an adversary from loading a bitstream Kronos did not produce. Encryption alone is not enough: without an authentication tag, a malleable ciphertext can be altered. Kronos requires authenticated encryption on every configuration load.

Order of operations

The device authenticates before it decrypts and configures - a fail-closed order. If the authentication tag over the encrypted bitstream does not verify against the device's provisioned key, configuration is refused and the node halts, feeding the same fail-closed path as secure boot.

python
# Load path: verify then decrypt (authenticated encryption, e.g. AES-GCM)
def load_bitstream(blob):
    hdr, ct, tag = parse(blob)
    if not aead_verify(ct, tag, key=device_key, aad=hdr):
        halt('bitstream auth failed')     # refuse before decrypt
    plain = aead_decrypt(ct, key=device_key)
    if hdr.design_id not in policy.allowed_designs:
        halt('unexpected design id')
    configure_fabric(plain)

Key handling

Design status

Authenticated-encryption load logic and version-monotonicity checks are implemented on development boards and modeled in the twin. Per-device key provisioning and the tamper-resistant key store are part of FOAK hardware manufacturing; no production reactor FPGA is yet fielded.

Content reviewed August 2026 · design-and-simulation stage