zeekayandHanzo Dev e4e70c888b fix(engine/chain): advance the durable sign floor from Quasar only, never Nova
The vote guard's finalizedThrough — a validator's PERMANENT, fsync'd
sign-refusal floor — was fed from Nova (bare-majority) acceptance through
four separate paths. Nova acceptance is reorgable by construction: at n=5,
its quorum intersection is 2a-n = 1, which is NOT > f=1, so a Nova height
may never become certified. Welding an irreversible refusal to it stranded
each validator at whatever it happened to accept first, and no restart,
resync, or peer could clear the refusal because it was already on disk.

That is mainnet 96369 at 1098192 and testnet 96368 at 11367: a valid block
was built, verified, and gossiped to every peer, but was unsignable, so no
certificate could ever assemble. Zero errors logged. It also made rolling
upgrades impossible, because a restarted node came back refusing exactly
the heights the fleet still needed it to sign.

Quasar is the only tier whose intersection exceeds f (strict 2/3 of 5 gives
2a-n = 3 > 1), so a Quasar height is agreed by every honest peer and may be
closed forever. Nova keeps everything it legitimately owns — the ledger,
VM.Accept, preference, catch-up, rejoin — and simply stops closing heights.

The four paths, all cut:
  - acceptWithCertCore no longer prunes/advances the guard on Nova accept
  - ingestAttestation advances it after PromoteQuasar reports advanced,
    fsync'd BEFORE the export frontier is published (so a crash cannot
    leave vm.LastQuasarHeight ahead of the compaction), fail-closed with
    an in-memory rollback and the observer withheld on write failure
  - SyncState (RLP import / state sync / snapshot clone) is a recovery
    hint again; block data is not a certificate, and an import happens
    precisely when a fleet is below quorum
  - the Start boot seed from vm.LastAccepted is gone; the boot floor comes
    from the guard file and the export frontier the chain manager re-seeds
    from vm.LastQuasarHeight. A node with none of the three is genuinely
    memoryless and now says so loudly instead of inventing a floor

Compacting at the Quasar height RETAINS every binding in (Quasar, Nova].
Those heights stay guarded individually — one signature each, enforced by
memory of the actual vote — rather than closed by a blunt permanent floor.
That window is where a rolling upgrade lives: a restarted node can re-issue
its outstanding vote so the certificate can finally form.

Renames, so the tiers cannot be re-braided by a later edit:
  GetDecidedFloor          -> GetNovaAcceptedFloor  (build/catch-up only)
  pruneCommittedSlotsBelow -> compactVoteGuardThroughQuasar
  new: GetQuasarSigningFloor — the only source for a permanent refusal

Deliberately NOT a tier gate at cert intake. An earlier attempt to refuse
Nova certs in HandleIncomingCert broke three heal/rejoin tests, because
Nova certs ARE the recovery transport; nova_quasar_matrix_test.go:319
requires a healed fleet to re-converge on Nova. All three stay green here.

No ava/snow imports added.

Tests: engine/chain full suite ok 211s. Negative control — re-introducing
the Nova weld fails 4 tests with the exact halt signatures. New
quasar_signing_floor_test.go covers: Nova accept leaves both frontier and
durable floor untouched; Quasar promotion advances floor + compaction in
one atomic write; guard write failure rolls back and withholds the export
frontier; RLP import above the floor stays signable; restart keeps the
floor at Quasar while every uncertified height stays individually bound and
idempotently re-signable. Two existing tests re-sourced from vm.LastAccepted
to the export frontier, each gaining the inverse assertion that the
Nova-only window stays signable.

Co-authored-by: Hanzo Dev <[email protected]>
2026-07-30 07:03:57 -07:00
2026-06-28 20:35:53 -07:00

consensus

Lux Consensus

Lux is not merely adding post-quantum signatures to a chain; it defines a hybrid finality architecture for DAG-native consensus, with protocol-agnostic threshold lifecycle, post-quantum threshold sealing, and cross-chain propagation of Horizon finality.

See LP-105 §Claims and evidence for the canonical claims/evidence table and the ten architectural commitments — single source of truth.

CI Status Go Version

Quasar Family of Consensus

Quasar is the consensus engine for the Lux network. It provides unified consensus for linear chains (P-Chain, C-Chain) and DAG chains (X-Chain) with post-quantum finality via three independent cryptographic signing paths.

Sub-Protocols

Protocol Role Package
Photon K-of-N committee selection via Fisher-Yates sampling with luminance-weighted reputation protocol/photon
Wave Per-round threshold voting with FPC (Fast Probabilistic Consensus) protocol/wave
Focus Confidence accumulation: beta consecutive successes = local finality protocol/focus
Nova Linear chain consensus mode (P-Chain, C-Chain) -- wraps Ray protocol/nova
Nebula DAG consensus mode (X-Chain) -- wraps Field protocol/nebula
Prism DAG geometry: frontiers, cuts, uniform peer sampling protocol/prism
Horizon DAG order-theory: reachability, LCA, transitive closure, skip lists protocol/horizon
Flare DAG certificate/skip detection via 2f+1 quorum protocol/flare
Ray Linear chain finality driver: Wave + Focus + Sink protocol/ray
Field DAG finality driver: Wave + safe-prefix commit protocol/field
Quasar BLS + Pulsar + ML-DSA threshold signing, epoch management protocol/quasar

Signing Modes

Each cryptographic layer is independently toggleable:

Mode Layers Use Case
BLS-only BLS12-381 threshold Fastest classical consensus
BLS + ML-DSA BLS + FIPS 204 ML-DSA-65 Dual with PQ identity proof
BLS + Pulsar BLS + Ring-LWE 2-round threshold Dual with PQ threshold proof
BLS + Pulsar + ML-DSA All three in parallel Full Quasar (triple mode)

IsTripleMode() returns true when all three paths are configured. TripleSignRound1 runs BLS + Pulsar + ML-DSA signing in parallel goroutines.

PQ Mode Selection (Configurable)

The active mode is selectable at runtime via config.PQMode or the CONSENSUS_PQ_MODE env var. Defined in config/pq_mode.go:

Mode Env value Maps to wire policy
BLSOnly bls PolicyQuorum
BLSPlusMLDSA bls-mldsa PolicyPQ
BLSPlusCorona bls-rt PolicyPZ
BLSPlusGroth16 bls-z PolicyQuantum (placeholder)
TripleQuantum triple PolicyQuantum

Run bench/pq_modes_bench_test.go for measured per-mode signing / aggregation / verify costs and cert sizes. Storage and cert size trade-offs:

Mode Sign Agg Verify Cert Storage 10K
bls 312 µs 8.6 ms 714 µs 123 B 1.17 MB
bls-mldsa 369 µs 8.5 ms 3.4 ms 69 KB 665 MB
bls-rt 39 ms 3.3 s 1.6 ms 33 KB 318 MB
triple 40 ms 3.3 s 4.3 ms 102 KB 981 MB

Pulsar / triple include the full 2-round Pulsar threshold protocol (github.com/luxfi/pulsar/threshold — Pulsar is Lux's variant with DKG2 and Pulsar-SHA3 hash suite). Production parameters M=8, N=7, LogN=8 (ring degree 256), Q=2^48-ish: classical 2^142, quantum 2^130. Cert-size floor of ~33 KB is set by the (C, Z, Delta) ring polynomials; protocol/quasar/cert_size_compare_test.go measures and verifies this.

Architecture

consensus/
  protocol/
    photon/       Committee selection (Emitter + Luminance)
    wave/         Threshold voting + FPC
      fpc/        Fast Probabilistic Consensus selector
    focus/        Confidence counter (beta tracker)
    prism/        DAG cuts, frontiers, uniform sampling
    horizon/      DAG reachability, LCA, skip lists
    flare/        DAG cert/skip classification (2f+1)
    ray/          Linear chain driver (Nova uses this)
    field/        DAG finality driver (Nebula uses this)
    nova/         Linear chain consensus mode
    nebula/       DAG consensus mode
    chain/        Block interface primitives
    quasar/       BLS + Pulsar + ML-DSA threshold signing
  engine/         Consensus engine (Chain, DAG, PQ wrappers)
  core/           Core types, DAG structures
  types/          Block, Vote, Config, Bag
  config/         Parameter presets (single, local, testnet, mainnet)
  runtime/        VM wiring (chain IDs, validators, logging)
  pkg/wire/       Wire protocol credentials (ML-DSA-44/65/87 + BLS + Ed25519)
  bench/          Benchmarks
  version/        Re-exports github.com/luxfi/version

Consensus Flow

Linear Chains (Nova)

Photon (select committee) -> Wave (threshold vote) -> Focus (count beta) -> Ray (decide) -> Sink

DAG Chains (Nebula)

Photon (select committee) -> Wave (threshold vote per frontier vertex)
  -> Flare (cert/skip) -> Horizon (safe prefix) -> Field (commit ordered prefix) -> Committer

Quasar PQ Finality

After consensus decision, the Quasar signing layer produces threshold certificates:

  1. BLS: single-round threshold share via crypto/threshold
  2. Pulsar: 2-round Ring-LWE threshold via luxfi/corona/threshold
  3. ML-DSA-65: single-round FIPS 204 identity signature

All three run in parallel. A block is quantum-final when all configured certificate layers are valid.

Key Hierarchy

Layer Key Type Purpose
Node-ID Ed25519 P2P transport auth
Validator-BLS BLS12-381 Classical finality votes
Validator-PQ Pulsar (Ring-LWE) PQ finality shares
Validator-ID ML-DSA-65 (FIPS 204) PQ identity attestation
Wallet (EVM) secp256k1 User transaction signatures
Wallet (X-Chain) secp256k1 UTXO locking

Quick Start

import "github.com/luxfi/consensus"

chain := consensus.NewChain(consensus.DefaultConfig())

ctx := context.Background()
if err := chain.Start(ctx); err != nil {
    log.Fatal(err)
}
defer chain.Stop()

block := &consensus.Block{
    ID:       consensus.NewID(),
    ParentID: consensus.GenesisID,
    Height:   1,
    Payload:  []byte("Hello, Lux!"),
}
if err := chain.Add(ctx, block); err != nil {
    log.Fatal(err)
}

Configuration

// Auto-configure based on validator count
params := consensus.GetConfig(21) // mainnet defaults

// Or use presets
consensus.SingleValidatorParams() // 1 node, dev
consensus.LocalParams()           // 5 nodes, local
consensus.TestnetParams()         // 11 nodes, testnet
consensus.MainnetParams()         // 21 nodes, production

Benchmarks

Measured on Apple M1 Max:

Component Operation Time/Op
Wave Vote round 3.38 us
Photon K-of-N selection 3.03 us
Luminance Brightness update 72 ns

ZAP wire protocol (measured, bench/):

Configuration Throughput
Single connection 114K TPS
20 parallel connections 376K TPS
50 conns + batch 1000 20.26M TPS

Testing

GOWORK=off go test ./...
GOWORK=off go test -bench=. ./bench/

Security Model

  1. Pre-quantum: Attacker must corrupt >= 1/3 stake to fork
  2. Q-day (BLS broken): Lattice certificates prevent unsafe finalization
  3. Post-quantum: Security rests on Module-LWE (Pulsar) + Module-LWE/SIS (ML-DSA)

License

BSD 3-Clause. See LICENSE.

S
Description
Quasar consensus engine: Go implementations of consensus protocols for the Lux Network.
Readme
251 MiB
Languages
Go 85.5%
Rust 7.6%
Python 3.1%
TeX 1.2%
C 0.9%
Other 1.7%