Darkmatter Exo 4.7 Beta 2 -

  • Rolling upgrade strategy:
  • Rollback: beta includes a fallback mode to start with legacy scheduler via runtime flag if regressions occur.
  • Example runtime flags:

    • When packet loss exceeds 12%, the FrodoKEM handshake fails to complete because of a tight timeout (currently 2.5 seconds). Workaround: use the TCP fallback mode (enabled via --proto tcp-only), though this sacrifices some metadata protection.

    As a Beta release, version 4.7b2 contains significant anomalies that operators must acknowledge: Darkmatter Exo 4.7 Beta 2

    | Feature | Exo 4.7 Beta 2 | Signal Protocol (Quantum Resistant variant) | WireGuard + QSC (experimental) | | --- | --- | --- | --- | | Quantum-resistant KEM | FrodoKEM-976 | Kyber-768 | None (classic only) | | Metadata protection | Full stripping + ANI | Partial (timing fixed) | None (IP headers exposed) | | Side-channel active defense | Yes (ANI) | No | No | | Latency overhead (handshake) | High (~210ms) | Medium (~90ms) | Low (~20ms) | | Production-ready | No (Beta) | Yes (but Kyber only) | No (research branch) | Rolling upgrade strategy:

    Clearly, Exo 4.7 Beta 2 is over-engineered for consumer use but extremely compelling for threat models that include nation-state side-channel analysis and harvest-now-decrypt-later quantum attacks. Rollback: beta includes a fallback mode to start