According to Midnight’s Node v1.0.400 release notes, released October 6, 2026, the update replaces the embedded Ledger dependency version 8.1.2 with 8.1.3. The new node also rejects contract calls containing non-canonical values or operations.
That wording matters. A canonical value is represented in the one encoding the system expects. If older software accepts multiple representations while newer software accepts only the canonical form, the two versions can reach different conclusions about a transaction. In a blockchain, that is not merely a compatibility nuisance. It can affect whether a proposed block is accepted.
Midnight’s release notes explicitly warn that Node v1.0.300 and Node v1.0.400 may disagree about the validity of transactions and blocks. The project is therefore asking operators to upgrade all nodes, with block producers first. Producers determine which transactions are assembled into blocks, so version skew among them can become a consensus risk multiplier even when no formal runtime upgrade is taking place.
The Ledger issue beneath the node
The underlying change comes from Ledger 8.1.3. Midnight’s Ledger v8.1.3 release notes describe the fix for the critical GHSA-wr7g-rr4v-jmj8 advisory as a requirement for canonical field-value encodings.
The stated security concern involves possible repeated one-time actions, including payouts. Ledger 8.1.3 also rejects related malformed transcript operations. The practical effect is that values and operations that could previously be interpreted in more than one acceptable way are now constrained by stricter validation.
That makes the update relevant beyond ordinary dependency hygiene. Midnight’s privacy architecture depends on software layers that interpret cryptographic data and contract activity correctly. A weakness in that lower-level logic can have consequences for action uniqueness and transaction validity, even if the network’s visible runtime and governance interfaces do not change.
The midnight-node v1.0.400 GitHub release characterizes the change as a binary-only security patch. It says the fix had already been deployed on Preview, Preprod and Mainnet, identifies the version skew between Ledger 8.1.2 and 8.1.3 as a consensus risk, and confirms that spec_version remains 1_000_300.
Why the coordination request matters
Because the patch leaves the runtime, RPC methods, configuration and chain specifications unchanged, operators might reasonably treat it as a routine binary replacement. That would miss the important distinction. A stable interface does not mean stable validation behavior.
The episode tests whether Midnight’s validator infrastructure can move in a coordinated way when a security fix changes the boundary between valid and invalid data. The network does not need a governance vote or a runtime migration for software versions to become economically significant. If block producers upgrade at different speeds, the result can be uncertainty over which chain history different operators recognize.
That does not mean the release represents a confirmed network failure. It means the project has identified a condition in which delay could increase risk. The clearest remedy is operational: upgrade block producers first, then complete the rollout across the remaining nodes.
For Midnight, the broader lesson is that privacy is not only a question of who can observe transaction data. It is also a question of whether every participant applies the same rules to the data that the system does expose. Here, the security boundary runs through a Ledger dependency, and maintaining that boundary requires coordination as much as code.
Jesica Davis is not a person. No notebook, no deadlines, no face behind the name — just a byline this newsroom publishes under. Here is the production line underneath it, because a name beside a portrait reads like a journalist, and this one is not one.
The models. Writing: gpt-5.6-luna and gpt-5.6-terra. Out on the live web: gpt-5.6-terra and gpt-5.6-luna. Pictures: gpt-image-1 and flux. Swap one in the newsroom and this line swaps with it — it is read off the machines, not typed here.
How a story is made
- Research. The searching model reads around the story, pointed at primary sources — the filing, the post, the repository — rather than at somebody else's write-up of them.
- Writing. The writing model drafts it against what was found, at Jesica Davis's usual length and in Jesica Davis's usual register.
- The loop. A reviewer reads the draft and sends it back with notes. Then reads it again. A piece can go round several times before it leaves the building.
- Enrichment. A quotation has to appear word for word on the page it is taken from. A chart may only use figures that appear in the source it cites. Whatever fails is dropped, and the reason is kept.
- Fact check. A last pass hunts for claims the article makes and its sources do not.
- A human stop. Sensitive subjects are held for a person to read before publication, and a person can kill any of it at any point.
If that sounds less like a newsroom and more like a factory: quite. It is called Press Factory.
This article was generated using AI and published automatically without human pre-publication review.
How this article was made
The article was produced by the Grandmonts Media News Engine using automated research, drafting and verification workflows. No human editor reviewed the article before publication. Grandmonts Media remains responsible for the published content. Errors can be reported at office@grandmonts.cz.