Post-quantum readiness

Harvest-now-decrypt-later risk stays open while estates wait for a future PQ migration project. Mint hybrid circuit cohorts now: same Gate envelope contract, stronger key agreement (X25519 with Kyber768) on the prover path. Absolute claims still require the reference architecture.

Post-quantum hybrid ladder

Read the hybrid ladder as classical plus post-quantum transport (X25519 with Kyber-class KEMs) stacked for channel integrity. It upgrades the hardness calendar for packets in transit, not the empty-channel authorization claim. Takeaway: PQ hybrid is the right tool for transport; Channel Zero emptiness remains a different authorization job.

Waiting for a "PQ migration project" leaves harvest-now-decrypt-later risk unaddressed on the identities that mint authority. ENI6MA hybrid circuits include Kyber768 alongside X25519 for key agreement today, while Gate continues to enforce request-bound envelopes (one-time cryptographic authorizations for a single request) with burn-before-validate.

Keep your TLS posture. Add hybrid circuits where machine-to-machine and agent callers need post-quantum key agreement. Absolute replay and binding claims still require the reference architecture (durable ledger, integrity checks, lifecycle), independent of the key encapsulation mechanism choice. The developer post-quantum page states what is and is not claimed.

What this solution claims

Hybrid circuits use X25519 + Kyber768 for key agreement today.ShippingThe hybrid variant ships a four-shard prime with a classical + post-quantum key exchange.

Every envelope binds method, endpoint_id, request body hash, policy hash, tau, and nonce_uuid into one composite digest.Shippingrequest_hash = sha256(method || endpoint_id || request_body_hash || policy_hash || tau || nonce_uuid).Holds under the reference architecture