What's New · 22 August 2026

NAVAL·SEM v2.0.1 — Packaging Fix

Bugfix Windows Packaging Bitcoin Timestamping
Released 22 August 2026 · Semantic version 2.0.1 · CC BY-NC-ND 4.0
🩹

Patch release — fixes v2.0.0's Bitcoin timestamping in packaged builds

A single, targeted fix so that anchor: true works correctly in the SourceForge/Windows installer build, not just when running from source. No API or schema changes.

Fixed · Packaged-Build Timestamping
🛠
Bitcoin timestamping failed to initialize in PyInstaller builds
naval_sem.spec · hidden imports · UPX exclusion

The v2.0.0 Bitcoin timestamping feature (introduced alongside the fingerprint/provenance system) worked correctly when running NAVAL-SEM from source, but failed to initialize in the compiled Windows binary distributed via SourceForge.

  • Root cause: opentimestamps and its dependencies (Cryptodome, bitcoin) weren't declared as PyInstaller hidden imports, so they weren't bundled correctly into the packaged executable.
  • Second issue: UPX compression, applied to reduce installer size, could corrupt Cryptodome's compiled extensions specifically on Windows.
  • Fix: added explicit hidden imports for the OpenTimestamps dependency chain and excluded Cryptodome from UPX compression in naval_sem.spec.
Migration

No API changes — upgrade if you use the anchor flag

If you build NAVAL-SEM from source, this release doesn't affect you directly. If you use the SourceForge/Windows installer and plan to set anchor: true on any endpoint, make sure you're on v2.0.1 or later — earlier packaged v2.0.0 builds will report the timestamp submission as failed even though the rest of the analysis completes normally.

Files Changed
naval_sem.spec
NAVAL·SEM v2.0.1 · CC BY-NC-ND 4.0 · GitHub · Zenodo DOI
Previous releases:   v2.0.0 v1.0.0 Full changelog →