Releases

Current release and history.

Every ZJX release since 1.21 STREAMWALL, newest first. Each shipped only after passing qualification.

Current release: ZJX 1.30.0

ZJX 1.30.0 is the current engine release. Against 1.29.7 it writes smaller archives in every compact and fast measurement, packs 1.5x to 4.1x faster in those objectives, and restores fast and ultrafast archives faster on all five public corpora, with the same archive format as the 1.29 line. Released on 2026-10-26 as tag v1.30.0 with the Linux x86-64 package and checksums; the package is available on request. Linux x86-64 with glibc.

Tag
v1.30.0
Package
zjx-1.30.0-linux-x86_64.tar.gz, 5,841,260 bytes, SHA-256 0bb42c9160f8287265e4cc91cb3b9eac8c429a19dd9e19b904b8c44cb381a7a6; the qualified binaries packaged unchanged
Previous release
ZJX 1.29.6.6, 2026-10-12

Get ZJX: availability, package access, licensing · The 1.29 support contract

ZJX 1.30.0 release artwork: the ZJX lattice cube compressing a wide field of signal lines into a narrower beam

ZJX 1.30.0

Released with its package and checksums2026-10-26Current release

Smaller and faster at once: against 1.29.7, compact and fast write smaller archives on all five public corpora (up to 25.7% smaller, Go source code in fast) and pack 1.5x to 4.1x faster, and fast and ultrafast archives restore faster on every corpus. Same archive format: 1.29.7 restored every 1.30.0 archive in the release measurements.

1.30.0 results against 1.29.7
compact: archive size and packing time against 1.29.7
CorpusArchivePacking
silesia8.66% smaller2.08x faster (222.9 s to 107.3 s)
Go 1.27.3 source code7.98% smaller2.14x faster (172.4 s to 80.7 s)
GH Archive, one day2.71% smaller4.09x faster (170.3 s to 41.6 s)
http_logs0.36% smaller3.44x faster (367.6 s to 107.0 s)
enwik80.25% smaller3.45x faster (295.9 s to 85.7 s)
fast: archive size, packing and restore time against 1.29.7
CorpusArchivePackingRestore
Go 1.27.3 source code25.72% smaller2.09x faster2.03x faster
silesia8.02% smaller1.52x faster1.48x faster
GH Archive, one day2.71% smaller2.57x faster1.24x faster
http_logs0.36% smaller2.39x faster2.22x faster
enwik80.25% smaller2.13x faster1.15x faster

ultrafast: 1.42x to 2.10x faster restores on all five corpora, with the same archives as 1.29.7. 1.29.7 restored every archive 1.30.0 wrote in these measurements. One laboratory host: AMD Ryzen 3 7330U, 4 cores / 8 threads, Ubuntu 24.04; medians, the two versions run in alternating order on each repetition, every restore checked against the content digest.

The 1.30.0 results on the benchmarks page

ZJX 1.29.7

Qualified; distributed only inside a later release2026-10-19

Lighter restores: extraction used 1.08x to 2.00x less CPU than 1.29.6.5 in every measured extraction cell, with identical output. Qualified and first distributed inside 1.30.0.

ZJX 1.29 line artwork: the lattice gauge at the red line, titled 1.29.5 to 1.29.6.6, the 1.29 line

ZJX 1.29.6.6

Released with its package and checksums2026-10-12

A reliability release for JSON-lines data, with full compatibility for archives written by earlier versions. Every other archive is byte-identical to 1.29.6.5, and creation and verification times are unchanged.

ZJX 1.29.6.5 SIGHTLINE

Released with its package and checksums2026-10-08

Faster on already-compressed media: on photos, video and other already-compressed files the fast objective is 1.14x to 12.80x faster in verified creation than 1.29.6, within 1% of its previous size. Every other archive is byte-identical to 1.29.6.

ZJX 1.29.6 IRONFLOOR

Released with its package and checksums2026-10-06

Faster than 1.29.0 in every measured cell: 1.74x verified creation across 48 cells (1.20x in the slowest cell), with byte-identical archives and lower peak memory, plus sealed and fresh holdout tiers.

1.29.6 IRONFLOOR results

Against released 1.29.0, on 48 primary cells: 1.74x faster verified creation overall and 1.20x in the slowest cell, 1.50x less CPU, and 3.27x lower peak memory. Faster than 1.29.0 in every measured cell (48 primary cells plus sealed and fresh holdout tiers) with byte-identical archives. One laboratory host: AMD Ryzen 3 7330U, 4 cores / 8 threads, Linux.

Results since 1.29.0

ZJX 1.29.5 GRIDMIND

Released with its package and checksums2026-09-24

An adaptive resource planner sizes each archive job to the machine it runs on: 1.36x faster verified creation than 1.29.0 overall on the qualification host, with archive bytes unchanged.

ZJX 1.29 REDLINE release artwork: a lattice gauge with its needle at the red line

ZJX 1.29.0 REDLINE

Released with its package and checksums2026-09-08

The speed-first release: a third creation objective, ultrafast, beside compact and fast, with a deterministic parallel packer and a streaming parallel verifier at four workers in the qualified speed configuration. Qualified verified-creation results against default tar | zstd -1, reported separately: 1.247x on the sealed development cohort (95% [1.223, 1.267]) and 1.1959x on a held-out cohort frozen before measurement (95% [1.1867, 1.2043]). Compact and fast stay byte-identical to 1.28.0. The qualified release build was promoted unchanged and reports the version literal 1.29.0-rc3.

REDLINE measurements
Verified creation of the 1.29.0 tested configuration (ultrafast, four workers, then an independent test); two campaigns reported apart
CampaignCohortAgainst default tar | zstd -1
Development cohortSealed development cohort: silesia, enwik8, and a synthetic deduplication case; 12 paired rounds, 468 of 468 cells usable1.247x faster; 95% [1.223, 1.267]; Bonferroni-adjusted lower bound 1.221
Held-out cohort (one shot)Four sealed members plus six privately held-out cases (about 1.86 GB, six workload classes) selected by a rule frozen before any measurement; ten classes, 12 paired rounds, 360 of 360 cells usable, run once1.1959x faster; 95% [1.1867, 1.2043]

Both headline figures compare ZJX ultrafast with four workers against default tar | zstd -1; the per-case results are on the benchmarks page. Against released 1.28.0 fast on the four-member cohort (diagnostic tier, four-member cohort including the service telemetry capture; 3 paired rounds): a creation ratio of 335x and a verified-creation ratio of 253x. The four-worker configuration admits about 65 MiB with the default settings and four workers (peak about 71 MB at four workers). Every admission is checked against the memory limit before work starts; an over-budget request is refused, never run with fewer workers.

Both campaigns in full, with per-case results

ZJX 1.28 LOCKWIRE release artwork: twisted safety wire sealing a row of bolts on a structural envelope

ZJX 1.28.0 LOCKWIRE

Released with its package and checksums2026-09-06

Product completion and release qualification: the complete Linux archive workflow, the fidelity contract, password-protected archives inherited from 1.27, machine-readable progress and cancellation, and a relocatable Linux x86-64 package with checksums, build provenance, and an offline restore guide. Archive bytes match 1.27 plus a 16-byte integrity footer.

ZJX 1.27 CIPHERGLASS release artwork: a sealed glass envelope holding a lock inside the lattice

ZJX 1.27 CIPHERGLASS

Qualified; distributed only inside a later release2026-09-05

Native password-protected archives: an ordinary archive wrapped in an authenticated-encryption envelope, so file names and metadata are encrypted with the contents. Qualified on Linux and first shipped inside 1.28.0.

ZJX 1.26 RELICWIRE release artwork: an engraved stone relic rewired with signal lines

ZJX 1.26 RELICWIRE

Tagged and chronicled; no published assets2026-09-04

Less creation time on the compact objective: about 28% less wall time and CPU on large single-file text and about 43% on a large mixed public corpus against 1.25.1, with 6/6 byte-identical archive pairs and 12/12 exact restores.

1.26 RELICWIRE measurements
1.26 RELICWIRE compact-mode comparison with ZJX 1.25.1
MeasurementResultScope
Large text: creation time and CPU~28% less wall time3/3 favourable comparisons
Large mixed corpus: creation time and CPU~43% less wall time3/3 favourable comparisons
Archive identity6/6 byte-identical pairsSecond-boot reproduction
Restoration compared with source12/12 exact restoresContents, permissions, nanosecond timestamps
Peak memory multiplierAbout 1.00Frozen allowance: 1.10

Measured against ZJX 1.25.1 NIGHTMARKET on the compact objective, on two large corpora and one controlled measurement host. Wall time and process CPU improved by about 28% on single-file text and about 43% on the mixed corpus.

ZJX 1.25.1 NIGHTMARKET release artwork: a row of luminous lattice market stalls

ZJX 1.25.1 NIGHTMARKET

Released with its package and checksums2026-09-02

The explicit choice between Compact and Fast. The frozen four-dataset campaign measured Fast at about 63.6% less creation time than Compact with no measured size penalty and 48/48 exact restores.

1.25.1 NIGHTMARKET measurements and scope

Frozen four-corpus clean-lab campaign: median creation-time fraction 0.3637 for Fast versus Compact (~63.6% less wall time, ~2.75x faster), 0 measured size penalty in the qualification campaign, 48/48 exact restores. Measured in the controlled 1.25.1 NIGHTMARKET qualification campaign. Figures come from the frozen laboratory host and the four corpora, commands, repetitions, and thresholds of that campaign.

ZJX 1.23 BLACKWIRE release artwork: a lattice converging into one black production wire

ZJX 1.23 BLACKWIRE

Released with its package and checksums2026-08-31

Native executable entry points for archive operations and the companion archive-bundle tool; the qualified workflow runs without Python or Node. Release and control archive bytes matched across seven datasets.

ZJX 1.21 STREAMWALL release artwork: data streams passing through a bounded lattice wall

ZJX 1.21 STREAMWALL

Released with its package and checksums2026-08-30

Enforceable memory and temporary-disk limits for creation, testing, and extraction. On Silesia it completed a 52,997,299-byte archive under a 1 GiB host ceiling and 768 MiB ZJX ceiling, then passed integrity and exact-restoration checks.

Its Silesia run completed at 390,225,920 bytes of peak encode RSS, about 95.5% below the 8,580,669,440-byte peak of the ZJX 1.2 historical reference.

How entries are labelled

  • Released: a tag with its Linux package and checksums; the package is available on request, and public release records are linked where they exist.
  • Qualified: passed its gates on the lineage but was distributed only inside a later release.
  • Promoted: tagged and chronicled without published assets.

Benchmark ledger