zeekay 1982a62421 fix: replace L2/subnet language with sovereign L1 across all docs
All Zoo, Hanzo, SPC, Pars, and Liquidity chains are sovereign L1s with
their own validator sets, not L2s or rollups.

Changes across 45 files:
- "L2 EVM" -> "Sovereign L1 EVM" in chain docs, bridge, wallet, SDK,
  operator, cloud, CLI, faucet, explorer, and all reference docs
- chains/evm.mdx title: "L2 EVM" -> "EVM Chains"
- deploy-subnet.mdx title: "Deploy an L2" -> "Deploy a Chain"
- CLI chain types: remove L2 default, L1 is now default
- Post-quantum doc: update Dilithium -> ML-DSA-65 (FIPS 204),
  Kyber -> ML-KEM-768 (FIPS 203), SPHINCS+ -> SLH-DSA (FIPS 205),
  mark Phase 1+2 as Deployed, Phase 3 as In Governance Review,
  add Quasar triple hybrid consensus (BLS + Corona + ML-DSA),
  add Smart Account PQ signing via SafeMLDSASigner (ERC-1271)
- plugins: "L2 EVM" alias -> "subnet-evm", fix URLs to luxfi/evm

Left as-is: SafeL2 (Gnosis Safe contract name), NIST L2 (security
level), L2 norm (math), Optimism/Polygon/Base (they are L2s),
LP proposal titles, Go struct names, wire protocol field names.
2026-04-09 21:17:53 -07:00
2026-02-14 05:26:19 -08:00

Lux Network Documentation

Official documentation for Lux Network - Post-quantum secure blockchain infrastructure.

Built with @hanzo/docs - the documentation framework by Hanzo AI.

Getting Started

# Install dependencies
pnpm install

# Start development server
pnpm dev

# Build for production
pnpm build

Documentation Structure

content/
└── docs/
    ├── index.mdx          # Welcome page
    ├── learn/             # Learning resources
    │   ├── introduction/  # Introduction to Lux
    │   ├── architecture/  # Architecture deep-dive
    │   └── consensus/     # Consensus mechanisms
    ├── build/             # Developer guides
    │   ├── quickstart/    # Quick start guide
    │   ├── sdk/           # SDK documentation
    │   └── contracts/     # Smart contract development
    ├── nodes/             # Node operation
    │   ├── run/           # Running a node
    │   ├── validators/    # Validator setup
    │   └── staking/       # Staking guide
    └── reference/         # API reference
        ├── api/           # REST/RPC API
        └── cli/           # CLI reference

Contributing

  1. Fork the repository
  2. Create your feature branch
  3. Add or modify documentation in content/docs/
  4. Submit a pull request

License

MIT © Lux Network


Part of the Hanzo Docs ecosystem.

S
Description
Documentation site for Lux Network's architecture, SDKs, and node operations.
Readme BSD-3-Clause
5.4 MiB
Languages
MDX 99.2%
TypeScript 0.8%