Files
hips/HIPs/hip-0005-post-quantum-security-for-ai-infrastructure.md
zeekayandHanzo Dev 7a9dcac628 What each runtime implements of the Hanzo corpus
An audit read the code and found the proposal that specifies it. Go reaches
all 122 capability proposals and 64 of the 121 other Standards Track ones;
Rust has 35, mostly the operator and the CLI; C++ has three, because the
complete original C++ in the estate is a ZAP handler, a bot nothing specifies,
and authored kernels inside forked CUDA and Metal crates.

    | | shipped | partial | none | not assessed |
    | Go   | 146 | 33 | 1 |  80 |
    | C++  |   1 |  2 | 0 | 257 |
    | Rust |  10 | 25 | 1 | 224 |

The large "not assessed" columns are the point rather than a gap. The model and
training specs are Python, the frontend and design-system proposals are
TypeScript, and recording `none` against those would read as a search that
came up empty when the honest statement is that the runtime was never the
question. Governance, Meta and Process are not graded at all.

Six proposals are Final with nothing found in Go and are left unwritten rather
than demoted: 0065, 0089, 0098, 0103, 0521 and 0902. HIP-0521 answers itself,
its own section reading "Not yet implemented". Three of the others name a
canonical Go file in consensus/protocol/auth that nobody wrote, in a package
where the four neighbouring proposals' files all exist with tests beside them.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-05 19:18:13 -07:00

3.2 KiB

hip, title, author, type, category, status, implementation-rust, implementation-go, created, requires
hip title author type category status implementation-rust implementation-go created requires
0005 Post-Quantum Security for AI Infrastructure Hanzo AI Team Standards Track Security Final partial partial 2024-12-20 LP-100

HIP-0005: Post-Quantum Security for AI Infrastructure

Abstract

This proposal mandates the integration of NIST Post-Quantum Cryptography standards across all Hanzo AI infrastructure, ensuring quantum-resistant security for AI models, data, and communications. Building on Lux Network's PQC implementation (LP-100), this extends quantum resistance to AI-specific operations.

Specification

PQC Algorithm Adoption

Inherit from Lux Network (LP-100):

  • ML-KEM-768: Default key encapsulation
  • ML-DSA-65: Default digital signatures
  • Hybrid Mode: ML-KEM + X25519 for defense-in-depth

AI-Specific Security Layers

Model Protection

pub struct SecureModel {
    // Model weights encrypted with ML-KEM
    encrypted_weights: Vec<u8>,
    // Signature for integrity
    signature: MlDsaSignature,
    // Encryption key wrapped with KEK
    wrapped_key: WrappedKey,
    // Privacy tier configuration
    privacy_tier: PrivacyTier,
}

Secure Inference Pipeline

  1. Input Encryption: Client encrypts input with ML-KEM
  2. TEE Processing: Computation in secure enclave
  3. Output Encryption: Results encrypted before transmission
  4. Audit Trail: ML-DSA signed logs

API Authentication

{
  "api_key_id": "ak_1234",
  "timestamp": 1703001234,
  "nonce": "random_value",
  "signature": {
    "algorithm": "ML-DSA-65",
    "value": "base64_signature"
  }
}

Privacy Tiers for AI

Tier Use Case Security Features
0 Public models Basic PQC encryption
1 User data + At-rest encryption
2 Proprietary models + TEE processing
3 Sensitive inference + GPU CC (H100)
4 Classified AI + Full TEE-I/O

Key Management

Hierarchical Key Structure

Root Key (ML-KEM-1024)
├── Model Encryption Keys (ML-KEM-768)
├── API Authentication Keys (ML-DSA-65)
├── Data Encryption Keys (ML-KEM-768)
└── Session Keys (Hybrid Mode)

Key Rotation Schedule

  • Root Keys: Annual rotation
  • Model Keys: Per version
  • API Keys: Monthly rotation
  • Session Keys: Per connection

Implementation Requirements

For AI Services

  1. All model storage uses ML-KEM encryption
  2. API requests require ML-DSA signatures
  3. Inter-service communication uses hybrid mode
  4. Audit logs are cryptographically signed

For Client SDKs

from hanzo import SecureClient

client = SecureClient(
    api_key="...",
    pqc_enabled=True,  # Default
    privacy_tier=2
)

# Automatic PQC encryption/signing
response = client.complete(
    model="HMM-32B",
    messages=[...]
)

lementation

References

  1. LP-100: NIST PQC Integration for Lux
  2. NIST PQC Project
  3. HIP-0003: Jin Multimodal AI Architecture

Copyright and related rights waived via CC0.