Repository navigation
Releases
compact-js v3.0.2
type: component-release-note
status: draft
component: compact-js
version: 3.0.2
component_class: library/SDK
template_blob_sha: f20b0b2a13f82201bb2ce3e2f60523c85bf7c751
template_commit_sha: 3cf24faefda49b1daa58e892ec641b6ca8a13b9c
generated: 2026-11-17
generator: component-rn-draft v1.4.2
tested_with_status: build-pins
compact-js 3.0.2
Metadata
- Release type: patch
Semver delta 3.0.1 to 3.0.2, taken fromversion.jsonand the three package manifests (commit 9ca8ed2). - Date: 2026-11-17 (owner-confirmed 2026-11-17)
- Sister-line note: —
- Environment: not environment-scoped — the packages carry both the ledger 8 (
/v8) and ledger 9 (/v9) eras, and a consumer selects one at import - Released artifact(s): three npm packages at 3.0.2 — see Artifacts
- Component class: library/SDK (drives which operator fields apply; see Deployment information below)
- Upgrade scope: N/A — library
- Reset required: N/A — library
- Governance action required: N/A — library
High-level summary
compact-js 3.0.2 is a dependency-promotion patch. The ledger 9 era is built against the final
@midnightntwrk/ledger-v9 1.0.2 and @midnightntwrk/onchain-runtime-v4 4.0.2 instead of the
release candidates 3.0.1 was built against, and the published manifests now declare those final
versions as their floor. No compact-js source file changed, and the ledger 8 era is untouched.
Audience
These notes are written for:
- Developers building DApps on the
@midnight-ntwrk/compact-jspackages. - Developers who pin compact-js transitively through a consuming SDK and care which ledger 9
binding resolves in their install tree. - Shielded Technologies engineering teams maintaining consuming SDKs.
Dependencies
- Requires
@midnightntwrk/ledger-v9>= 1.0.2 for the ledger 9 era; the manifest declares
^1.0.2. - Requires
@midnightntwrk/onchain-runtime-v4>= 4.0.2 - The compact runtime pin is unchanged at the exact version 0.21.0, so the compactc 0.36
requirement introduced in 3.0.0 carries over unaltered. - The ledger 8 era stays on
@midnightntwrk/ledger-v88.1.3 over compact runtime 0.16.0.
Downstream impact (cascading effects). A consuming SDK or DApp that takes compact-js 3.0.2
resolves the final ledger 9 binding and on-chain runtime rather than a release candidate, which
is the pair compact-js itself was built and tested against at this version (package.json,
yarn.lock at commit 9ca8ed2). @midnight-ntwrk/compact-runtime 0.21.0 declares ^4.0.0-rc.3 for the
on-chain runtime; ^4.0.2 intersects it at 4.0.2 and above, so a fresh install still resolves a
single copy (package.json). Consumers that carry their own resolutions or overrides entry
pinning @midnightntwrk/onchain-runtime-v4 to 4.0.2-rc.0 should drop it. Nothing a consumer
depends on differs between the release candidates and the finals: the Ledger 9.1.0.2 release note
describes 9.1.0.2 as a post-QA promotion of 9.1.0.2-rc.0 whose only post-candidate movement was in
the proof server, and the component owner confirms the bindings carry no consumer-visible change
(owner-confirmed 2026-11-17).
Tested-with versions
Read from the package manifests and the lockfile at this revision: these are build pins — not QA-verified.
| Component | Tested-with version |
|---|---|
compact runtime (@midnight-ntwrk/compact-runtime) |
0.21.0 (package.json) |
| compact toolchain/compiler (compactc) | 0.36.0 (3.0.0 release body; the runtime pin it was read against is unchanged) |
ledger 9 bindings (@midnightntwrk/ledger-v9) |
1.0.2 (package.json) |
ledger 8 bindings (@midnightntwrk/ledger-v8) |
8.1.3 (package.json) |
on-chain runtime (@midnightntwrk/onchain-runtime-v4) |
4.0.2 (package.json) |
compact runtime, ledger 8 era (@midnight-ntwrk/compact-runtime) |
0.16.0 (package.json) |
The ledger rows name npm binding packages, which version independently of the ledger component
release line: @midnightntwrk/ledger-v9 1.0.2 is a binding version, not a ledger 9.1.0.x version.
Deployment information
- Upgrade scope: N/A — library
- Reset required: N/A — library
- Governance action required: N/A — library
- Downtime / coordination: N/A — library
Artifacts
@midnight-ntwrk/compact-js@3.0.2— core execution environment@midnight-ntwrk/compact-js-node@3.0.2— Node.js implementations of the service types@midnight-ntwrk/compact-js-command@3.0.2— CLI for executing compiled contracts
What changed
- Built the ledger 9 era against the final 1.0.2 bindings (PR #54) —
@midnightntwrk/ledger-v9
1.0.2 and@midnightntwrk/onchain-runtime-v44.0.2, replacing the 1.0.2-rc.0 and 4.0.2-rc.0
release candidates 3.0.1 resolved. - Raised the declared dependency floors in the published manifests (commit 9ca8ed2) from
^1.0.2-rc.0and^4.0.0-rc.3to^1.0.2and^4.0.2. - Changed no source file (commit 9ca8ed2): the release touches the package manifests, the
lockfile andversion.jsononly.
New features
None.
New features requiring configuration updates
None.
Improvements
Published dependency floors name the versions the release was built against
Description: per package.json, the manifests shipped with 3.0.1 declared
@midnightntwrk/ledger-v9 ^1.0.2-rc.0 and @midnightntwrk/onchain-runtime-v4 ^4.0.0-rc.3,
while the monorepo's resolutions entry built and tested that release against 4.0.2-rc.0 — so the
versions a consumer resolved were not the versions the release was verified on. In 3.0.2 the
declared floors, the lockfile and the resolutions entry all name the same final versions, 1.0.2
and 4.0.2 (commit 9ca8ed2).
Deprecations
None.
Breaking changes
None.
Known issues
compact-js and compact runtime declare different on-chain runtime ranges
Description: per compact-js issue #42,
@midnight-ntwrk/compact-js declares ^4.0.2 for @midnightntwrk/onchain-runtime-v4 while its
own dependency @midnight-ntwrk/compact-runtime 0.21.0 declares ^4.0.0-rc.3. The two ranges
intersect at 4.0.2 and above, so a fresh install today resolves one copy; the ranges are still
not written as one, and two resolved copies reject each other's WASM objects.
Workaround (if any): pin @midnightntwrk/onchain-runtime-v4 to a single version through the
consuming project's resolutions or overrides entry if an install tree does resolve two copies.
CompiledContract context fails across identical package copies
Description: per compact-js issue #28,
when two identical copies of a compiled contract package are resolved in one process, building a
contract context fails with a raw constructor TypeError.
Workaround (if any): deduplicate the contract package so a single copy is resolved.
A valid null --input-ps is rejected
Description: per compact-js issue #30,
the CLI's circuit command rejects a valid null --input-ps, so a contract whose initial private
state is null cannot be run from the CLI.
Workaround (if any): give the contract a non-null initial private state.
Links and references
- QA test coverage / test evidence: qa/tests/evidence/3.0.2/README.md (on
main; added after the release, so not in the tag) - PRs: compact-js PR #54
- Engineering docs: Ledger 9.1.0.2 release note
- SDK docs:
@midnight-ntwrk/compact-json npm - Known issues board: compact-js issues
- Related component releases: Ledger 9.1.0.2 and Proof Server 9.0.2
Fixed defect list
No compact-js defect is recorded as fixed in 3.0.2. The release moves dependency pins only, and
the ledger-side fixes carried by the 1.0.2 bindings reached consumers in 3.0.1, which already
resolved the 1.0.2-rc.0 candidate.
compact-js v3.0.1
compact-js-v3.0.1 Release compact-js-v3.0.1
compact-js v3.0.1-rc.2
compact-js 3.0.1-rc.2
Metadata
- Release type: patch
- Date: 2026-11-13
- Sister-line note: —
- Environment: Preview
- Released artifact(s): 3 npm packages at 3.0.1-rc.2 — see Artifacts
- Component class: library/SDK (drives which operator fields apply; see Deployment information below)
- Upgrade scope: N/A — library
- Reset required: N/A — library
- Governance action required: N/A — library
The packages are not themselves environment-scoped: they carry both the ledger 8 (/v8) and
ledger 9 (/v9) eras, and a consumer selects one at import.
High-level summary
This is a pre-release build for Preview; it is not a production release.
compact-js 3.0.1-rc.2 moves the toolchain this release is built and tested against: the compactc
pin goes to 0.36.1, and the workspace now resolves @midnightntwrk/onchain-runtime-v4 to
4.0.2-rc.0 (commit 1b0b9d4). Both are build-time changes. No compact-js source file
changed, no published dependency range moved, and contracts compiled for the ledger 9 era on
3.0.0 or 3.0.1-rc.1 run unchanged.
Audience
These notes are written for:
- Developers building DApps on the
@midnight-ntwrk/compact-jspackages. - Developers who compile Compact contracts with compactc and execute them from TypeScript.
- Shielded Technologies engineering teams maintaining consuming SDKs.
Dependencies
- Requires compactc 0.36 for contracts executed on the ledger 9 era. 3.0.0's recompilation
requirement is unchanged, and taking this release needs no further recompilation. compactc
0.36.1 is a patch on the same toolchain line and reports the same Compact runtime version,
0.21.0 (compactc 0.36.1 release note). - Still requires an ESM-capable consumer.
- Pairs with ledger 9.1.0.2-rc.0. The ledger binding is a release candidate, so the fee and
gas-accounting behaviour it carries can still change before the stable 9.1.0.2. - The ledger 8 era (
/v8,/v8/effect) is untouched.
Downstream impact (cascading effects). The on-chain runtime pin added in this release lives
in the workspace root resolutions block, which is not part of any published package manifest —
the published @midnight-ntwrk/compact-js@3.0.1-rc.2 still declares
@midnightntwrk/onchain-runtime-v4 as ^4.0.0-rc.3 (npm). A consumer installing this release
therefore resolves that range themselves, to 4.0.1, and does not inherit 4.0.2-rc.0. The pin
states what compact-js was built and tested against, not what a consumer gets. A consumer that
wants to match this build must pin @midnightntwrk/onchain-runtime-v4 to 4.0.2-rc.0 in their own
project. Otherwise this release is a drop-in for 3.0.1-rc.1.
Tested-with versions
Read from the package manifests, the workspace lockfile and the CI environment file at this tag:
these are build pins — not QA-verified.
| Component | Tested-with version |
|---|---|
compact runtime (@midnight-ntwrk/compact-runtime) |
0.21.0 (package.json) |
| compact toolchain/compiler (compactc) | 0.36.1 (commit 1b0b9d4) |
ledger 9 bindings (@midnightntwrk/ledger-v9) |
1.0.2-rc.0 (package.json) |
ledger 8 bindings (@midnightntwrk/ledger-v8) |
8.1.3 (package.json) |
on-chain runtime (@midnightntwrk/onchain-runtime-v4) |
4.0.2-rc.0 — build only; published range is ^4.0.0-rc.3, which resolves 4.0.1 for consumers (package.json, commit 1b0b9d4) |
compact runtime, ledger 8 era (@midnight-ntwrk/compact-runtime) |
0.16.0 (package.json) |
platform-js (@midnight-ntwrk/platform-js) |
3.0.0 (package.json) |
wallet SDK address format (@midnight-ntwrk/wallet-sdk-address-format) |
3.1.0 (package.json) |
The ledger rows name npm binding packages, which version independently of the ledger component
release line.
Deployment information
- Upgrade scope: N/A — library
- Reset required: N/A — library
- Governance action required: N/A — library
- Downtime / coordination: N/A — library
Artifacts
@midnight-ntwrk/compact-js@3.0.1-rc.2— Typescript-based execution environment for smart contracts compiled with the Compact language (npm)@midnight-ntwrk/compact-js-node@3.0.1-rc.2— Platform specific types and utilities for working with the Compact language on a Node.js runtime (npm)@midnight-ntwrk/compact-js-command@3.0.1-rc.2— Command line utilities for working with smart contracts compiled with the Compact language (npm)
All three publish under the rc dist-tag; latest stays on 3.0.0 (npm).
What changed
- Raised the compactc pin used to build and test this release from 0.36.0 to 0.36.1 (PR #51, commit 1b0b9d4).
- Pinned the workspace resolution of
@midnightntwrk/onchain-runtime-v4to 4.0.2-rc.0 (commit 1b0b9d4). - Bumped the three package versions to 3.0.1-rc.2 for release (commit a55d3cf).
New features
None.
New features requiring configuration updates
None.
Improvements
compactc pin raised to 0.36.1
Description (commit 1b0b9d4): the compiler version this release is built and tested against
moves from 0.36.0 to 0.36.1. It is the version CI installs and the version the test
contracts are compiled with, so the ledger 9 era is now exercised end to end against 0.36.1
output. 0.36.1 is a patch release on the same toolchain line, keeping Compact language 0.28.0 and
Compact runtime 0.21.0; it fixes a key-generation crash for circuits using the JubjubScalar and
JubjubPoint types, and an internal compiler error for circuits using deserialized Boolean
values (compactc 0.36.1 release note).
Those two fixes are compactc's own; compact-js's behaviour on a given compiled contract is
unchanged. Contracts already compiled with 0.36.0 do not need recompiling to take this release.
On-chain runtime resolution pinned to 4.0.2-rc.0 for the build
Description (commit 1b0b9d4): the workspace root resolutions block now pins
@midnightntwrk/onchain-runtime-v4 to 4.0.2-rc.0. Before this, the
descriptors in the dependency tree resolved to a mix of versions; they now collapse to one. This
makes the on-chain runtime that compact-js is tested against explicit and reproducible instead of
floating with the registry. The pin is a workspace build-time construct and is not published:
see Dependencies for what a consumer actually resolves.
Deprecations
None.
Breaking changes
None. Nothing in compact-js's own API moves in this release, and no published dependency range
changes (npm). The on-chain runtime resolution pin to 4.0.2-rc.0 carries no consumer-visible
behaviour change and is filed as an improvement (owner-confirmed 2026-11-13).
Known issues
CompiledContract context fails across identical package copies
Description (carried forward from the 3.0.1-rc.1 release body; still open at this tag): when
two identical copies of a compiled contract package are resolved in one process, building a
contract context fails with a raw constructor TypeError
(compact-js issue #28).
Workaround (if any): deduplicate the contract package so a single copy is resolved.
A valid null --input-ps is rejected
Description (carried forward from the 3.0.1-rc.1 release body; still open at this tag): the
CLI's circuit command rejects a valid null --input-ps, so a contract whose initial private
state is null cannot be run from the CLI
(compact-js issue #30).
Workaround (if any): give the contract a non-null initial private state.
3.0.1-rc.0 and 3.0.1-rc.1 both listed a third known issue — verifier-key removal transactions
rejected with BalanceCheckOverspend
(midnight-node issue #2375). That
issue was closed on 2026-11-12 as not reproducible on 2.1.101, and is resolved rather than
outstanding at this release (owner-confirmed 2026-11-13).
Links and references
- QA test coverage / test evidence: — (no QA evidence is published for this release candidate; owner-confirmed 2026-11-13)
- PRs: PR #51 — bump compact and pin onchain-runtime
- Engineering docs: Compact toolchain 0.36.1 release note
- Migration guides: — (no migration needed from 3.0.1-rc.1)
- SDK docs:
@midnight-ntwrk/compact-json npm - Known issues board: compact-js issues
- Public schema: — (the component publishes no GraphQL, OpenAPI or ABI schema)
- API documentation: — (the TypeScript declarations shipped in the packages are the API reference)
- Related component releases: Ledger 9.1.0.2-rc.0
Fixed defect list
The following defects were fixed in 3.0.1-rc.2.
None. The two compiler defects this release picks up are fixed in compactc 0.36.1, not in
compact-js — see Improvements (compactc 0.36.1 release note).
compact-js v3.0.1-rc.1
compact-js 3.0.1-rc.1
Metadata
- Release type: patch
- Sister-line note: —
- Date: 2026-11-12
- Environment: not environment-scoped — the packages carry both the ledger 8 (
/v8) and ledger 9 (/v9) eras, and a consumer selects one at import - Released artifact(s): 3 npm packages at 3.0.1-rc.0 — see Artifacts
- Component class: library/SDK (drives which operator fields apply; see Deployment information below)
- Upgrade scope: N/A — library
- Reset required: N/A — library
- Governance action required: N/A — library
High-level summary
compact-js 3.0.1-rc.1 repoints the ledger 9 era at the bindings for ledger 9.1.0.2-rc.0 —
@midnightntwrk/ledger-v9 1.0.2-rc.0 over @midnightntwrk/onchain-runtime-v4 ^4.0.0-rc.3
(resolving 4.0.1), the same range @midnight-ntwrk/compact-runtime 0.21.0 requests.
Nothing in compact-js's own API moves, and contracts compiled for the ledger 9 era on 3.0.0 run
unchanged. This is a release candidate built on release-candidate ledger bindings, so it is for
testing against ledger 9.1.0.2-rc.0 rather than for production use.
Audience
These notes are written for:
- Developers building DApps on the
@midnight-ntwrk/compact-jspackages. - Developers who compile Compact contracts with compactc and execute them from TypeScript.
- Shielded Technologies engineering teams maintaining consuming SDKs.
Dependencies
- Still requires compactc 0.36 for contracts executed on the ledger 9 era; 3.0.0's recompilation
requirement is unchanged and no further recompilation is needed to take this release. - Still requires an ESM-capable consumer.
- Pairs with ledger 9.1.0.2-rc.0. The ledger binding is a release candidate, so the fee and
gas-accounting behaviour it carries can still change before the stable 9.1.0.2. - The ledger 8 era (
/v8,/v8/effect) is untouched.
Downstream impact (cascading effects). A consuming SDK or DApp taking this release inherits
the 1.0.2-rc.0 ledger binding for its ledger 9 path and should pin to it deliberately rather than
through a range, so the binding cannot move underneath an already-tested build. Consumers holding
both eras in one process keep their ledger 8 artefacts as they are.
Tested-with versions
Read from the package manifests and the CI environment at this tag: these are build pins — not QA-verified.
| Component | Tested-with version |
|---|---|
compact runtime (@midnight-ntwrk/compact-runtime) |
0.21.0 |
| compact toolchain/compiler (compactc) | 0.36.0 |
ledger 9 bindings (@midnightntwrk/ledger-v9) |
1.0.2-rc.0 |
ledger 8 bindings (@midnightntwrk/ledger-v8) |
8.1.3 |
on-chain runtime (@midnightntwrk/onchain-runtime-v4) |
4.0.1 (declared ^4.0.0-rc.3) |
compact runtime, ledger 8 era (@midnight-ntwrk/compact-runtime) |
0.16.0 |
platform-js (@midnight-ntwrk/platform-js) |
3.0.0 |
wallet SDK address format (@midnight-ntwrk/wallet-sdk-address-format) |
3.1.0 |
The ledger rows name npm binding packages, which version independently of the ledger component release line.
Deployment information
- Upgrade scope: N/A — library
- Reset required: N/A — library
- Governance action required: N/A — library
- Downtime / coordination: N/A — library
Artifacts
@midnight-ntwrk/compact-js@3.0.1-rc.0— Typescript-based execution environment for smart contracts compiled with the Compact language@midnight-ntwrk/compact-js-node@3.0.1-rc.0— Platform specific types and utilities for working with the Compact language on a Node.js runtime@midnight-ntwrk/compact-js-command@3.0.1-rc.0— Command line utilities for working with smart contracts compiled with the Compact language
What changed
- Ledger 9 moves to the
1.0.2-rc.0binding line (commit ddd493b).
New features
None.
New features requiring configuration updates
None.
Improvements
Ledger 9 moves to the 1.0.2-rc.0 binding line
Description: Ledger 9 moves to the 1.0.2-rc.0 binding line. The era now builds against
@midnightntwrk/ledger-v9 1.0.2-rc.0 over @midnightntwrk/onchain-runtime-v4 ^4.0.0-rc.3 —
the range @midnight-ntwrk/compact-runtime 0.21.0 itself requests, so the pair shares one
on-chain runtime instance rather than loading a second. These are the bindings for ledger
9.1.0.2-rc.0, which partitions transcripts against a mock transaction's
size and time-to-dismiss and rehearses calls with the widest commitment tree indices. The
binding adds TransactionShape and an optional expected-shape argument to
partitionTranscripts; neither is re-exported through the Ledger facade, so compact-js's own
API is unchanged. The ledger 8 era is untouched. (commit ddd493b)
Deprecations
None.
Breaking changes
None.
Known issues
All three were open at 3.0.0 and remain open at this release.
Verifier-key removal transactions are rejected with BalanceCheckOverspend
Description: a maintenance transaction that removes a verifier key fails the balance check
although the ledger bindings report it as paid, which affects the v4 maintenance updates built
by ContractExecutable (midnight-node issue #2375).
Workaround (if any): none in compact-js — the fix is in the ledger's fee calculation and
reaches consumers when they pick up the ledger release that carries it.
CompiledContract context fails across identical package copies
Description: when two identical copies of a compiled contract package are resolved in one
process, building a contract context fails with a raw constructor TypeError
(compact-js issue #28).
Workaround (if any): deduplicate the contract package so a single copy is resolved.
A valid null --input-ps is rejected
Description: the CLI's circuit command rejects a valid null --input-ps, so a contract
whose initial private state is null cannot be run from the CLI
(compact-js issue #30).
Workaround (if any): give the contract a non-null initial private state.
Links and references
- QA test coverage / test evidence: —
- PRs: compact-js pull requests merged for this release
- Engineering docs: Compact toolchain 0.36.0 release note
- Migration guides: — (no migration needed from 3.0.0)
- SDK docs:
@midnight-ntwrk/compact-json npm - Known issues board: compact-js issues
- Public schema: —
- API documentation: —
- Related component releases: Ledger 9.1.0.2-rc.0 and Proof Server 9.0.2-rc.0
Fixed defect list
The following defects were fixed in 3.0.1-rc.0.
None.
compact-js v3.0.1-rc.0
compact-js-v3.0.1-rc.0 Release compact-js-v3.0.1-rc.0
compact-js v3.0.0
Metadata
- Release type: major
- Sister-line note: —
- Date: 2026-11-05
- Environment: not environment-scoped — the packages carry both the ledger 8 (
/v8) and ledger 9 (/v9) eras, and a consumer selects one at import - Released artifact(s): three npm packages at 3.0.0 — see Artifacts
- Component class: library/SDK (drives which operator fields apply; see Deployment information below)
- Upgrade scope: N/A — library
- Reset required: N/A — library
- Governance action required: N/A — library
High-level summary
compact-js 3.0.0 moves the ledger 9 era onto compact runtime 0.21 and compactc 0.36, and builds
ledger 9 against @midnightntwrk/ledger-v9 1.0.0. The three packages now publish as ESM only.
Contracts compiled with compactc 0.35 or earlier have to be recompiled to run on the ledger 9
era, and that has consequences for contracts already deployed — the Breaking changes section
below carries the detail. The ledger 8 era is untouched.
Audience
These notes are written for:
- Developers building DApps on the
@midnight-ntwrk/compact-jspackages. - Developers who compile Compact contracts with compactc and execute them from TypeScript.
- Shielded Technologies engineering teams maintaining consuming SDKs.
Dependencies
- Requires compactc 0.36 for contracts executed on the ledger 9 era: artefacts from compactc 0.35
or earlier declare compact runtime 0.20 and fail the runtime version check on import
(commit bfa165f). - Requires an ESM-capable consumer: a CommonJS
requireof these packages resolves only through
Node'srequire(esm)support (commit 2a0fa26). - The ledger 8 era (
/v8,/v8/effect) stays on compact runtime 0.16 and takes no recompilation
(commit bfa165f).
Downstream impact (cascading effects). A consuming SDK or DApp that takes compact-js 3.0.0 for
its ledger 9 path inherits the compactc 0.36 requirement for every contract it executes on that
era, and has to ship ESM. Consumers holding both eras in one process keep their ledger 8 artefacts
as they are.
Midnight.js 5.0.0 pins compact-js 3.0.0, so DApps on Midnight.js 5.0.0 take on the compactc 0.36 recompile and ESM-only requirements for the ledger 9 path. Midnight.js 4.x users are not affected.
Tested-with versions
Read from the package manifests and the CI environment at this tag: these are build pins — not QA-verified.
| Component | Tested-with version |
|---|---|
compact runtime (@midnight-ntwrk/compact-runtime) |
0.21.0 |
| compact toolchain/compiler (compactc) | 0.36.0 |
ledger 9 bindings (@midnightntwrk/ledger-v9) |
1.0.0 |
ledger 8 bindings (@midnightntwrk/ledger-v8) |
8.1.3 |
on-chain runtime (@midnightntwrk/onchain-runtime-v4) |
4.0.0 |
compact runtime, ledger 8 era (@midnight-ntwrk/compact-runtime) |
0.16.0 |
platform-js (@midnight-ntwrk/platform-js) |
3.0.0 |
wallet SDK (@midnightntwrk/wallet-sdk) |
— |
| proof server | 9.0.0 |
| node | 2.1.101 |
| indexer | 4.4.101 |
| midnight.js | — |
Sources for the filled rows: package.json at the tag for every npm pin, commit bfa165f for the
compactc version, and the component owner for the proof server, node
and indexer rows (owner-confirmed 2026-11-05).
The ledger rows name npm binding packages, which version independently of the ledger component
release line: @midnightntwrk/ledger-v9 1.0.0 is a binding version, not a ledger 9.1.0.x version.
Deployment information
- Upgrade scope: N/A — library
- Reset required: N/A — library
- Governance action required: N/A — library
- Downtime / coordination: N/A — library
Artifacts
@midnight-ntwrk/compact-js@3.0.0— core execution environment; sha1385647b7d3d83633d76aed6ba982fd9db0f13587(npm)@midnight-ntwrk/compact-js-node@3.0.0— Node.js implementations of the service types; sha16cc47aa38fcf8ffc25d1e2d760526cca82dc0840(npm)@midnight-ntwrk/compact-js-command@3.0.0— CLI for executing compiled contracts; sha1cdcdd514e3303002ad06eb78dd667ba873a9af42(npm)
What changed
- Moved the ledger 9 era to compact runtime 0.21 and compactc 0.36 (PR #40).
- Built ledger 9 against
@midnightntwrk/ledger-v91.0.0 and pinned the on-chain runtime to 4.0.0 (PR #41). - Fixed the gas-budget rejection of calls that overwrite existing ledger state (PR #38).
- Moved the ledger 8 era to the final
@midnightntwrk/ledger-v88.1.3 (commit 11d098a). - Removed the CommonJS build; the packages publish as ESM only (commit 2a0fa26).
- Release plumbing and version bumps across the release-candidate line are not listed individually (PR #39).
New features
Era-selectable entry points
Description: the packages expose /v8, /v8/effect, /v9 and /v9/effect beside the unsuffixed entry, so a consumer picks the ledger era at import rather than taking whichever era the package binds; both eras can be live in one process, and the unsuffixed entry remains the default for a configuration that names no era (package.json).
New features requiring configuration updates
Contract artefacts compiled with compactc 0.36
Required updates: before the first run on this release.
- Recompile ledger 9 contract sources with compactc 0.36 and repoint the ZK asset paths at the new output (commit bfa165f).
- Leave ledger 8 artefacts on the toolchain that produced them; the
/v8entry is unchanged (commit bfa165f).
Impact: artefacts built by compactc 0.35 or earlier declare compact runtime 0.20 and are
rejected by the runtime version check on import, so a ledger 9 configuration cannot load them.
Read the Breaking changes section before recompiling a contract that is already deployed.
Improvements
Gas-budget accounting for state-overwriting calls
Description: with @midnightntwrk/ledger-v9 1.0.0 the transcripts are partitioned with the cost model of midnight-node 2.1.100-rc.4, and calls that overwrite existing ledger state no longer fail the gas-budget check (commit a75c0f3, owner-confirmed 2026-11-05).
Deprecations
None.
Breaking changes
Contracts for the ledger 9 era have to be recompiled with compactc 0.36
What changed: the ledger 9 era pairs with compact runtime line 0.21 over on-chain runtime v4, so Ledger.era.runtime and CompactRuntime.line read 0.21 on the unsuffixed and /v9 entries (commit bfa165f).
What breaks: artefacts produced by compactc 0.35 or earlier declare runtime 0.20 and fail the runtime version check on import; and because recompiling changes a contract's verifier keys, a contract that is already deployed cannot simply be re-attached with freshly compiled artefacts — the new keys do not match the keys in the deployed contract's state, and the attach is rejected (commit bfa165f).
Required actions: for every affected consumer.
- Recompile ledger 9 contract sources with compactc 0.36 before running them on this release (commit bfa165f).
- For a contract already deployed, pick one of three routes instead of re-attaching: keep the deployed artefacts and the toolchain that built them; add the recompiled verifier keys through the contract's maintenance authority, which the ledger keeps beside the existing ZKIR v2 keys, so the old keys need not be removed; or redeploy the contract at a new address (see the Compact toolchain 0.36.0 release note).
- Pin the toolchain version in CI so a routine rebuild cannot change the keys of a deployed contract (commit bfa165f).
Code example: recompiling a contract for the ledger 9 era.
compact compile --version 0.36 src/counter.compact build/counterCircuits declared in a contract type can no longer be pure
What changed: every circuit declared in a contract type has to carry a proof, because the ledger matches a cross-contract call against the called circuit's proof; declaring such a circuit pure is a compile-time error, and purity is gone from the runtime's cross-contract API (commit bfa165f).
What breaks: a contract type carrying a pure circuit declaration stops compiling, and code reading the removed purity fields stops type-checking (commit bfa165f).
Required actions: for every affected consumer.
- Remove
purefrom circuit declarations in contract types, and fromcontract implementsdeclarations whose implementing circuit ispure(commit bfa165f). - Disclose the arguments of every cross-contract call; the exemption that applied to
purecircuits is gone with those declarations (commit bfa165f).
Code example: a contract-type circuit declaration.
// was: pure circuit foo(x: Field): Field;
circuit foo(x: Field): Field;
Cross-contract calls have to be recompiled
What changed: a cross-contract call's proof now binds the callee circuit named at the call site, which the compiler emits as a constant of the call site (commit 444ac16).
What breaks: a contract making cross-contract calls that is not recompiled produces calls whose proofs do not bind the callee (commit 444ac16).
Required actions: for every affected consumer.
- Recompile every contract that makes a cross-contract call, callee side included (commit 444ac16).
- For a caller that is already deployed, adding keys is not enough: its old keys must also be removed, because they still accept proofs from the unfixed circuit. Verifier-key removal is affected by the first known issue below, so until that is fixed, redeploy the caller instead.
Code example: no source change is needed — the behaviour comes from recompiling.
compact compile --version 0.36 src/caller.compact build/callerLedger 9 contract operation version moves from v3 to v4
What changed: compactc 0.36 emits only ZKIR v3 verifie...
compact-js v3.0.0-rc.6
compact-js-v3.0.0-rc.6 Release compact-js-v3.0.0-rc.6
compact-js v3.0.0-rc.5
compact-js-v3.0.0-rc.5 Release compact-js-v3.0.0-rc.5
compact-js v3.0.0-rc.4
compact-js-v3.0.0-rc.4 Release compact-js-v3.0.0-rc.4