Engine

PhoenixSig

The signing engine that powers every Phoenix product. Epoch-based keys, deterministic state evolution, and automatic recovery after breach. Not a standalone product — the engine behind Attestation, Chain, and Cloud.

Three mandatory layers

PhoenixSig treats every signature as a temporary state snapshot, not a permanent operation.

PQC Engine

ML-DSA (FIPS 204) + SLH-DSA (FIPS 205) as signing backends. Dual algorithm coverage. PhoenixSig manages key lifecycle — PQC just signs.

DyLWE Core

Deterministic state evolution on module ring R_q. Forward-only progression. No external randomness. Every state transition auditable and reproducible.

Phoenix Injection

TEE-backed VaultKey provides hardware entropy for post-compromise recovery. After refresh, all future keys change completely. Attacker's snapshot becomes useless.

How PhoenixSig works

Deterministic Key Derivation

seed_epoch = HKDF(VaultKey ∥ sigma ∥ context). Every signing key is fully deterministic, dependent on hardware secret + evolving state + message policy. Reproducible yet unpredictable.

Merkle Key Commitment

All epoch public keys committed to a Merkle tree. Verifiers only need root hash + current epoch proof. Efficient O(log n) verification.

Quarantine Mode

On reboot, suspected compromise, or sync loss: refresh_pending = true. Device signs only pings/dummy data until hardware confirms fresh entropy injection.

GenericPCSWrapper

Algorithm-agnostic implementation. Wrap any PQC algorithm (current or future) in PCS guarantees within one day. Mathematical verification via FormalPCSModel.

Where PhoenixSig powers Phoenix products

Integrate PhoenixSig

Start with Quantum Attestation — the fastest path to post-quantum security.