Post-quantum blockchain with multi-consensus architecture, fully homomorphic encryption (FHE), and cross-chain interoperability. High-performance decentralized infrastructure for the next generation of secure, scalable applications.

Lux features the Quasar consensus family, multi-chain architecture (X-Chain DAG, P-Chain platform, C-Chain EVM, custom subnets), and an integrated post-quantum cryptography stack including lattice-based signatures, FHE, and threshold MPC.

# Install Lux CLI
go install github.com/luxfi/cli@latest

# Create a local network
lux network start

# Deploy a chain
lux chain create L1
lux chain deploy L1

Chains:     X-Chain (DAG)  |  P-Chain (Platform)  |  C-Chain (EVM)  |  Subnets
                           |
Consensus:  Quasar Family -- Snowball, Snowflake, Avalanche, Frosty, P3Q
                           |
Crypto:     Lattice signatures  |  FHE  |  Threshold MPC  |  Zero-knowledge
                           |
Bridge:     Teleport -- Zero-knowledge MPC cross-chain bridge

Lux ships a deliberate three-tier IP strategy: public BSD-3 commodity, patent-protected Lux Ecosystem License with paid commercial license available, and a closed-source private performance tier living in lux-private/* (private GitHub org). Read this section before forking, embedding, or building a commercial product on top of Lux code.

Definitions of "Authorized Network", "Descending Chain", "Research Use", and "Commercial Use" are the ones in the Lux Ecosystem License v1.2 text — see any Eco-tier repo's LICENSE for the binding language. Where this README and the LICENSE disagree, the LICENSE wins.

A common point of confusion: every Lux artifact is licensed. The question is not "is there a license" — it is "which license, and is there a runtime token check on top of it". The table below separates those two concerns.

Two things this table makes explicit:

1. The public CPU binary is not "unlicensed". It ships under BSD-3-Clause (or, for vendored upstreams, the inherited Apache / MIT / GPL / LGPL / MPL / BSL). What it lacks is a runtime token check, because there is nothing in that binary to gate.
2. The runtime token gate at cevm v0.50.0 and later only fires on tier-3 GPU/FPGA backends. CPU paths run unmodified under their actual public licenses. Removing or bypassing the token does not make the closed code free — the closed code never shipped in the public binary in the first place (two-binary distribution).

The table below mirrors the LICENSE file currently in each public repository. The LICENSE file is the binding artifact; this table is a navigational aid.

Repositories not listed above either have no LICENSE file (treat as all-rights-reserved, contact licensing@lux.network) or are vendored upstream forks where the inherited LICENSE is the binding artifact.

coreth, evm, evmgpu carry LGPL-3.0 because they originate from go-ethereum. explore carries GPL-3.0 from Blockscout. safe-* carry GPL-3.0 from Safe (Gnosis). uni-v*-subgraph carry GPL-3.0 from Uniswap. czmq carries MPL-2.0 from upstream. None of these will be relicensed — the LICENSE is what governs use. The forward-looking replacements live in luxcpp/* (e.g. luxcpp/cevm is Apache-2.0 and is the going-forward EVM kernel; the LGPL evm repo will be retired as luxcpp/cevm reaches feature parity).

lux-private/* is the closed-source private GitHub organization that holds the production performance moat. It is currently being bootstrapped. The following are slated for extraction out of the public surface and into lux-private/* once the org is provisioned and the responsible engineers are added as members. Until extraction completes, the binding license is whatever the public repo's LICENSE declares.

Treat anything in lux-private/* as commercial-only. There is no public read access. There is no implied license. Use is governed exclusively by a signed commercial agreement.

Every public repository carries a top-level LICENSING.md pointing back to this document for context. The LICENSE file in each repo is the binding artifact. This page is documentation, not a license.

• Papers -- research papers (LaTeX)
• Security -- cryptographic audit trail
• License text repo -- canonical license text

• lux.network -- Website
• docs.lux.network -- Documentation
• explorer.lux.network -- Block explorer

Built by the Lux team in collaboration with Hanzo AI