Releases
A release is a version of the protocol — the contracts, the circuits, and
the interfaces to them. It is not an npm publish: the @nokto-protocol/*
packages are not on any registry, and every one of them carries
"private": true.
Each release has one page. That page states what existed at that version, what it was verified against, which assumptions were load-bearing, and what could not be done. The newest release page is the answer to "is this true today". Older pages are frozen: they are never edited to reflect later knowledge, only superseded.
When a snapshot is cut
When the protocol changes. Not when Midnight does.
An upstream bump — a new compiler, a new client stack, a new ledger — does not
cut a release. It opens a re-verification item against the current record, and
the build fails until toolchain.json and the current release page agree with
the repository again. That failure is the point: an assumption verified against
one toolchain is not an assumption about the protocol, it is an assumption
about a pair, and Midnight moves.
Cutting a release means: the packages move version in lockstep, a new page is
added here with status: current, the previous page becomes superseded, and
a tag lands on the commit that adds the record.
What is enforced
- Every release page carries the same seven sections, in the same order.
- The newest release's
verified againstmatrix must equaltoolchain.json, which in turn must equal the versions actually pinned across the workspace and thepragma language_versionon every contract that declares one. - Every release page appears in the table below.
Older releases are checked for structure and never for pins. They are records of a moment, and the moment does not move.
Record
| Version | Date | Status | Summary |
|---|---|---|---|
| v0.1.0 | 2026-08-31 | Current | First record. Phase 1a at the simulator level; five load-bearing assumptions confirmed by execution; the devnet level blocked upstream. |