mirror of
https://github.com/luxfi/consensus.git
synced 2026-09-24 00:26:58 +00:00
The Go-side Ringtail purge (commits6f8f8a22,dc7e4ed0,85b6e80f) was not propagated to pkg/rust prose. README, Cargo.toml description, and the top-level //! docstring in src/lib.rs still said "BLS12-381 + Ringtail" or "BLS + Ringtail signatures" while the Go consensus stack renamed to Pulsar (Module-LWE) + Corona (Ring-LWE) per LP-4200. Update README + Cargo.toml description + lib.rs //! header to use "Pulsar (Module-LWE threshold, FIPS 204 byte-equal)" — matching the canonical naming in consensus/CLAUDE.md. Cargo.lock 1.22.0 → 1.22.1 was already in the working tree from the pending version bump; commits alongside this prose alignment so the next crates.io publish carries both. NOT renamed: public API field names (ringtail_sig, ringtail_pubkey, collect_ringtail_signatures, etc.) — breaking surface renames need a deliberate decision and a coordinated minor/major bump. Prose alignment is the safe patch. `cargo check --no-default-features` PASS.