Calix Chain
Layer 1 · Post-quantum ready

The blockchain built for the quantum era.

Calix Chain is a sovereign Layer 1 with a full EVM, native token standards and NIST-standardised post-quantum cryptography — ML-KEM-768 for key encapsulation and ML-DSA-65 for digital signatures — engineered in from the first block, not bolted on later.

NIST FIPS 203 · ML-KEM-768NIST FIPS 204 · ML-DSA-65EVM compatibleCosmos SDK · CometBFTIBC ready
Latest block
—
Active validators
—
Network
—
PQC suite
ML-KEM-768
ML-DSA-65
Why post-quantum

Today's signatures and key exchange will not survive a quantum computer.

Elliptic-curve cryptography secures almost every blockchain in production. Shor's algorithm breaks it outright on a large enough quantum computer — and ledgers are permanent, so data recorded today can be attacked tomorrow.

◈

Harvest now, decrypt later

Adversaries can record encrypted traffic and on-chain ciphertext today and decrypt it once quantum hardware matures. Key encapsulation has to be quantum-safe before the threat is real.

◇

Forgeable signatures

A public key that has ever been exposed on chain can, in principle, be inverted to its private key. Lattice-based signatures remove that class of attack for good.

◉

Standards, not experiments

NIST finalised ML-KEM (FIPS 203) and ML-DSA (FIPS 204) in 2024. Calix builds on the standardised algorithms rather than proprietary schemes.

Technology

Two NIST standards. One post-quantum layer.

Both primitives are lattice-based (Module-LWE and Module-SIS), implemented in a memory-safe Rust core with a Go binding used directly by the chain.

FIPS 203 · Key encapsulation

ML-KEM-768

Addresses register an ML-KEM-768 encapsulation key on chain. Anyone can then derive a shared secret with them and encrypt data end-to-end with AES-256-GCM — ciphertext that stays confidential even against a quantum adversary.

Security categoryNIST Level 3 (≈ AES-192)
Encapsulation key1,184 bytes
Ciphertext1,088 bytes
Shared secret32 bytes
Hybrid payload cipherAES-256-GCM
On-chain modulex/pqc — key registry
FIPS 204 · Digital signatures

ML-DSA-65

A lattice-based signature scheme (derived from CRYSTALS-Dilithium) with deterministic key generation from a 32-byte seed, hedged signing and context strings. Verified byte-for-byte against NIST ACVP test vectors.

Security categoryNIST Level 3
Public key1,952 bytes
Signature3,309 bytes
Secret key4,032 bytes (or 32-byte seed)
Signing modePure interface, hedged, ctx ≤ 255 B
ConformanceNIST ACVP keyGen + sigVer vectors

Sizes are those of the FIPS parameter sets. The PQC library is open to inspection by auditors on request.

Architecture

A modular stack, sovereign by design.

Calix Chain is assembled from battle-tested Cosmos components and extended with its own execution and cryptography modules.

Application

dApps · DEX · Bridge · Wallets

Solidity contracts, CosmWasm contracts and native CLX20 / CLX721 / CLX1155 assets share one ledger.

Execution

EVM · CosmWasm · Native token modules

Ethereum JSON-RPC, MetaMask-compatible transactions, plus token standards implemented as chain modules for lower gas and stronger guarantees.

Post-quantum

x/pqc · ML-KEM-768 · ML-DSA-65

On-chain registry of post-quantum encapsulation keys, encrypted transfer messages, and the signature primitives backing the migration path.

Consensus & networking

CometBFT · Proof-of-Stake · IBC

Instant deterministic finality, delegated staking with slashing, and inter-blockchain communication with the Cosmos ecosystem.

Platform

Everything a production Layer 1 needs.

⚡

Fast, final blocks

CometBFT gives one-block deterministic finality — no reorgs, no waiting for confirmations.

⬡

Full EVM compatibility

Deploy existing Solidity contracts and use familiar tooling — Hardhat, ethers, MetaMask.

◆

Native token standards

CLX20, CLX721 and CLX1155 are chain modules, not contracts: cheaper to use and not exposed to contract-level bugs.

⇄

IBC & bridge

Connect to the Cosmos ecosystem through IBC and move assets to other chains through the Calix bridge relayer.

⚙

CosmWasm contracts

A second, Rust-based smart-contract runtime for applications that want stronger isolation.

⛨

Proof-of-Stake security

Bonded validators, delegation, on-chain governance and slashing keep the network honest and upgradeable.

Transparency

Exactly where post-quantum stands today.

Cryptography deserves precise claims. This is what is live, what is in progress and what is planned.

Component
What it does
Status
ML-KEM-768 key registry
x/pqc stores a validated encapsulation key per address (FIPS 203 type-check on registration).
Live on testnet
Hybrid encryption
ML-KEM-768 + AES-256-GCM client library for end-to-end encrypted payloads and encrypted transfer messages.
Live on testnet
ML-DSA-65 signatures
Key generation, signing and verification, checked against NIST ACVP vectors.
Implemented · verified
Native PQC transaction signing
Accept ML-DSA-65 signatures as an account authentication method alongside classical keys.
In progress
Hybrid consensus keys
Migrate validator and account keys from classical curves to hybrid classical + PQC.
Roadmap
Developers

Point your tools at Calix Chain.

Standard Ethereum tooling works out of the box. Add the network to your wallet or script against the JSON-RPC.

NetworkCalix Chain Testnet (calix-test-1)
EVM chain ID999 (0x3e7)
Native currencyCLX (6 decimals native · 18 in EVM)
ConsensusCometBFT 0.38 · Proof-of-Stake
Address formatscalix1… (Bech32) · 0x… (EVM)
InterfacesJSON-RPC · Cosmos REST · gRPC · CometBFT RPC
 Query the chain ID
# JSON-RPC · eth_chainId
curl -s -X POST $CALIX_RPC \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,
       "method":"eth_chainId","params":[]}'

# → {"jsonrpc":"2.0","id":1,"result":"0x3e7"}

Public RPC endpoints are published with the open testnet programme.

Build on the first post-quantum Layer 1 from day one.

Join the testnet, deploy a contract, register a post-quantum key.