the crate version no longer collides with what is published

Cargo.toml said 1.22.1, and 1.22.1 is on crates.io — published
2026-05-13, unyanked, 235 downloads. That published build is the one
whose verify_certificate ends

    !cert.aggregated_sig.is_empty() || !cert.quantum_sigs.is_empty()

so it accepts a certificate carrying no signature at all. Leaving this
tree at the same number says the fix and the forgery are the same
release. They are not. 1.22.2.

The removal of the aggregate path changes the public API, so whoever
publishes may prefer 2.0.0; the number here is the smallest one that
stops the collision.

Co-authored-by: Hanzo Dev <[email protected]>

pkg/rust/Cargo.lock

@@ -360,7 +360,7 @@ checksum = "34080505efa8e45a4b816c349525ebe327ceaa8559756f0356cba97ef3bf7432"
 
 [[package]]
 name = "lux-consensus"
-version = "1.22.1"
+version = "1.22.2"
 dependencies = [
  "blake3",
  "blst",

pkg/rust/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "lux-consensus"
-version = "1.22.1"
+version = "1.22.2"
 edition = "2021"
 description = "Lux Consensus SDK — pure-Rust Quasar post-quantum probabilistic consensus (Wave / FPC / Photon / Focus / Quasar PQ finality via hybrid BLS12-381 + Pulsar = P3Q)"
 license-file = "LICENSE"