FractalAI is the first AI-native Layer 1 blockchain built from scratch in Rust. It features post-quantum cryptography (CRYSTALS-Dilithium), Proof of Fractal Work consensus, WASM smart contracts, and 460+ RPC endpoints.

What is the FRAC token?

FRAC is the native utility token of the FractalAI blockchain with a fixed supply of 1 billion tokens. It is used for staking, governance, gas fees, and DeFi. FRAC is purely deflationary with a 61.8% fee burn rate based on the golden ratio.

How does Proof of Fractal Work differ from Proof of Work?

Proof of Fractal Work (PoFW) requires validators to perform fractal analysis instead of hash puzzles. Validators whose fractal dimensions approach the golden ratio (φ = 1.618) receive higher rewards, making it computationally meaningful rather than wasteful.

Is FractalAI quantum-resistant?

Yes. FractalAI uses CRYSTALS-Dilithium for digital signatures and Kyber for encryption, both NIST-approved post-quantum cryptographic algorithms that protect against quantum computing threats.

How can I buy FRAC tokens?

FRAC tokens are available through the presale at fractalai.net.co/presale. You can pay with USDC on Base, USDC on Stellar (lowest fees), or credit/debit card via Circle. The presale has 4 phases starting at $0.25 (Seed) up to $0.80 (Public), with listing target at $1.00.

What is the AURUM protocol?

AURUM is FractalAI's commodity tokenization protocol that enables gold, silver, platinum, and 5 other commodities to be tokenized on-chain with phi-bonding curves that grow at 1.618% per epoch.

← Learn

#cnsa 2.0#nsa post-quantum#national security algorithm suite

What is CNSA 2.0 and how to prepare for it

CNSA 2.0 — the Commercial National Security Algorithm Suite 2.0 — is the U.S. National Security Agency designation of the cryptographic algorithms required to protect national security systems in the post-quantum era. It names ML-KEM and ML-DSA as the quantum-resistant standards and sets a phased transition timeline running through the early 2030s, making post-quantum cryptography a procurement requirement for defense suppliers rather than an optional upgrade.

What CNSA 2.0 mandates

CNSA 2.0 specifies the approved algorithms and their roles for national security systems: ML-KEM (FIPS 203) for key establishment and ML-DSA (FIPS 204) for signatures, alongside hash-based signing for firmware and software where appropriate, and larger symmetric and hash parameters. Crucially it attaches dates — a staged schedule by which classes of systems, including software and firmware signing, must adopt the suite. For vendors selling into national security programs, meeting CNSA 2.0 on time becomes a condition of doing business.

How to prepare

Start with a cryptographic inventory: find every place your products and services use cryptography and record which algorithm, where, and protecting what. Build crypto-agility so primitives can be swapped without re-architecture. Prioritize long-lived and firmware-embedded signing, which cannot be patched later at scale. Then be ready to demonstrate readiness to program offices — increasingly that means producing a machine-readable cryptographic bill of materials rather than asserting compliance in a slide.

Honest scope

CNSA 2.0 governs which algorithms protect national security systems; adopting the named standards is necessary but not the whole of security, which still spans key management, supply chain and operations. The algorithms are resistant to known classical and quantum attacks per NIST and NSA analysis — a rigorous bar, not a permanent mathematical guarantee. Preparation is fundamentally about inventory and agility: you cannot migrate what you have not mapped, and program offices will ask you to prove the map.

Try it yourself — live, free, verifiable in 30 seconds:

Prove PQC readiness with a signed CBOM →