Midnight says in its Compact toolchain 0.36.0 release notes that the compiler now generates only ZKIR v3. ZKIR is the intermediate artifact used in Midnight’s zero-knowledge contract workflow. The practical effect is that developers cannot continue generating older ZKIR outputs with the new Compact version.

That change becomes more important when verifier keys are involved. Contracts compiled with older versions may use keys that are no longer suitable for the new artifacts. Recompiling those contracts changes their verifier keys, according to the release notes. Teams may therefore need to replace the keys associated with an existing deployment or redeploy the contract.

This is not necessarily a requirement to redeploy every contract on the network. It is a compatibility problem that depends on how a project was compiled, which verifier keys it uses and whether its deployment can accept the new artifacts. The risk is operational rather than theoretical. A contract can remain present on a network while its surrounding build and verification pipeline no longer matches the version expected by the updated toolchain.

The impact is broader for applications that call more than one contract. Midnight says cross-contract callers and callees require coordinated upgrades because the release changes circuit declarations and the Compact runtime. A caller updated in isolation may not be enough if the contract it invokes still follows the previous interface or artifact assumptions.

That coordination requirement matters for decentralized applications, libraries and deployment systems. Teams need to identify contracts that call other contracts, update both sides where necessary and confirm that the resulting verifier keys and generated artifacts match. Auditors also need to review whether a recompilation changes the material they previously examined. A compiler update can therefore create a new review boundary even when the business logic appears unchanged.

Midnight’s Ledger 9 mainnet announcement says the network hard fork was scheduled for November 6, 2026. The upgrade moves the network to ZKIR v3 and introduces signature support and composable contracts on mainnet. Those features expand what applications can build, but they also explain why the ecosystem cannot treat Ledger 9 as a routine node upgrade.

Signature support adds another way for applications to authorize or structure activity. Composable contracts allow contracts to work together more directly. Both features depend on applications using compatible declarations, runtimes and client tooling. The result is a network upgrade with a developer migration attached to it.

Midnight’s Ledger 9 operational guide lists the compatibility set required for the transition. It includes Compact 0.36.0, Compact runtime 0.21.0, Midnight.js 5.0.0 and proof server 9.0.0. The guide also describes migration steps for deployed contracts and decentralized applications.

That version list should be treated as a deployment matrix, not a suggestion to update one package and test later. A project using the new compiler with an old runtime, client library or proof server may produce a different class of failure from a contract that was never recompiled. Developers need to check the full path from circuit declarations to proof generation, transaction construction and on-chain verification.

The release also changes the meaning of “compatible” for Midnight applications. It is no longer enough for a contract to exist on Ledger 9 or for a compiler command to complete successfully. The generated artifact, verifier key, runtime, proof server and calling contract must agree on the same transition.

For developers, the immediate task is inventory. Identify deployed contracts, record their compiler and verifier-key versions, map cross-contract calls, then test recompilation in a controlled environment. For infrastructure teams, the priority is upgrading the listed components together. For auditors, the key question is whether a changed key or circuit declaration requires a fresh review.

Midnight’s privacy stack is becoming more capable through Ledger 9, but the upgrade makes its operational demands clearer. ZKIR v3 is the new baseline. Projects that plan for coordinated migration can use the new composability and signature features. Projects that treat Compact 0.36.0 as a simple compiler bump risk mismatched keys, failed calls and deployments that need to be rebuilt.

#Midnight#Compact#ZKIR v3#Ledger 9#zero-knowledge proofs#smart contracts#verifier keys#composable contracts#developer tools#blockchain upgrades

Noah Brown 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 Noah Brown's usual length and in Noah Brown'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.