zeekay
b70f60dc31
primitives/hash.go: PRNGKey / GenerateMAC / GaussianHash / PRF / Hash / LowNormHash all take HashSuite as first param. suite == nil resolves to the production default Pulsar-SHA3 (cSHAKE256 / KMAC256 / TupleHash256 per FIPS 202 + NIST SP 800-185). sign/sign.go: Party gains Suite field; NewParty defaults to hash.Default(); NewPartyWithSuite for operator-explicit construction. sign.Verify keeps its signature for callers and resolves the default internally; the suite-explicit form is sign.VerifyWithSuite. reshare/commit.go: suite-aware commit derivation aligned with the new hash.HashSuite contract used by the rest of pulsar/reshare/dkg2/keyera. Closes the gap where the HIP-0077 claim that Pulsar uses SHA-3 cSHAKE256/KMAC256/TupleHash256 in production was structurally false at the Sign layer (only pulsar/reshare/, pulsar/dkg2/, pulsar/keyera/ were consuming pulsar/hash/HashSuite previously). Pulsar-BLAKE3 retained as legacy/non-normative only for cross-port byte checks. go.mod: luxfi/math v1.3.0 -> v1.4.0 (consumes the codec for the new hash-suite tag). CHANGELOG.md added. sign_roundtrip_test.go pins the new contract. Tests: primitives + sign + reshare PASS. Patch-bump.
Pulsar
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.
Pulsar is the Lux-evolved post-quantum threshold signature stack for Quasar consensus, derived from daryakaviani/corona (academic 2-round threshold signature from LWE) with the protocol additions needed to operate on a leaderless open public chain.
Why "Pulsar"
Lux (Latin) → light. Pulsar → SI unit of luminous flux. Each validator emits a "pulsar" of signature toward consensus; aggregated, they form the chain's overall light. Brand-paired with Quasar (the consensus that consumes them).
Relationship to upstream Corona
The upstream repo at daryakaviani/corona is an academic proof-of-concept ("not ready for production use" per its README). Pulsar is the production track:
| Layer | Upstream Corona | Pulsar |
|---|---|---|
| 2-round threshold sign | ✅ same byte-equal protocol | ✅ inherited |
| Trusted-dealer Gen | ✅ for fixed federation | ✅ retained for bridge MPC |
| Proactive resharing for epoch validator rotation | ❌ not specified | 🚧 pulsar/reshare/ (this fork) |
| Pedersen DKG over R_q with proper hiding | ❌ not specified | 🚧 pulsar/dkg2/ (this fork) |
| Per-validator triple-sign integration with Quasar | ❌ N/A | 🚧 pulsar/consensus/ integration |
Layout
sign/— 2-round threshold signing (byte-equal with upstream)primitives/— Shamir, hashes, MACs, PRFs (byte-equal with upstream)utils/— NTT, Montgomery, ring helpers (byte-equal with upstream)networking/— TCP peer-to-peer (byte-equal with upstream)dkg/— original Lux DKG (Feldman VSS without noise; broken for public broadcast — see RED-DKG-REVIEW). Retained for reference.dkg2/— proper Pedersen DKG over R_q (Pulsar addition; this fork)reshare/— proactive secret resharing for epoch rotation (Pulsar addition; this fork)cmd/— KAT oracle generators
Status
WIP. The 2-round Sign+Verify path is byte-equal-validated against the academic Corona spec via 16 SHA-256 KATs. The Pulsar-specific additions (resharing + Pedersen DKG) are under design and implementation.