01 / NATIVE LAYER
Ed25519
Solana’s high-performance signature path stays present for the speed and compatibility the network expects.
Protocol signal / V6
Analux is quantum-resistant transfer architecture for Solana.
Made by Kingston Clifton
Scroll to enter the vault
The Analux signal
Analux preserves the familiar Solana transaction path, then gives it a second cryptographic proof built for a world where the old public-key assumptions have a deadline.
Our signature system
Every protected action is designed to keep the native authorization path intact while adding a compact, lattice-based Falcon-512 signature over the same intent.
01 / NATIVE LAYER
Solana’s high-performance signature path stays present for the speed and compatibility the network expects.
02 / QUANTUM LAYER
Our post-quantum layer adds lattice-based verification without turning the transaction into an oversized packet.
Q-Vault / MSS
Q‑Vault is the V6 quantum-resistant custody design currently in development. It is designed to hold protected assets at a Program Derived Address and release them only when the stitched Falcon-512 proof verifies the whole transaction state.
See how it stitchesMatching-Signature Stitching
MSS binds the entire transaction state before it is verified. We stitch the instruction, native signature, recent blockhash, and account nonce into one payload for Falcon-512.
ADKI-512
Analux Dual-Key Identity 512 brings the conventional key and the post-quantum key into a single account identity. Both layers must agree before protected assets move.
Analux public identity
DQIP / quantum insurance
Falcon verification needs real validator compute. V6 frames Dynamic Quantum Insurance Premium as a minimum priority-fee guard that keeps the verification path resourced—without a weaker off switch.
MINIMUM DQIP PRIORITY-FEE GUARD
V6 specifies a 1,000,000-lamport minimum for a protected release, aligning validator resources with the extra verification work.
THE REASON IT’S MANDATORY
Optional protection would create a weaker path around the system. Analux treats the second signature as a requirement, not a toggle.
Integrity, bound in time
Q‑Vault’s stitched state gives each protected transfer a complete cryptographic context: it is bound to its instruction, its temporal window, and its account-specific state.
Changing a destination, amount, or instruction changes the stitched payload. Verification fails before a protected release.
A recent blockhash and account nonce anchor each proof in time, so an intercepted signature cannot simply be used again later.
Protected assets live at a Program Derived Address. The vault program—not a curve private key—governs their release.
V6 / tests & internal audits
V6 records internal devnet and testnet validation around the Q‑Vault path: post-quantum checks, uploads, asset controls, replay resistance, and transaction-shape safeguards.
Internal checks cover the 897-byte Falcon-512 public key, 1024-byte prepared key, and 666-byte compressed signature flow.
Payload assembly and PDA structural checks were exercised with upload chunks capped at 700 bytes.
Internal coverage includes the null-freeze asset guard, sequential nonce behavior, and replay-defense paths.
Transaction-shape and compute-budget guards use a 1,000,000-lamport minimum DQIP and a 1,400,000-CU ceiling.
Internal tests and audits are not an external audit, production certification, or guarantee. Q‑Vault remains in development; an independent external audit is planned before launch.
The path ahead
The Analux roadmap tracks eight phases—from publication and Q‑Vault development through internal validation, the planned external audit, token launch, and validator-level implementation. Dates remain subject to change.

Open a channel
Talk to the Analux team about the Q‑Chain, Q‑Vault, or quantum-resistant transfer architecture.
analuxsupport@gmail.com