In a November 5, 2026 article, Midnight CTO Sebastien Guillemot explained how shielded assets can elevate on-chain security. His argument is that privacy is not simply about concealing transactions from public view. It is a security boundary that limits what attackers can learn about balances, ownership and payment relationships.
That distinction matters because public ledger data can be used as reconnaissance. If an attacker can identify a wallet’s holdings, follow its transactions and infer who controls it, the blockchain may provide much of the information needed to tailor a phishing attempt or other social engineering campaign. Shielding that information does not eliminate every threat, but it can reduce the intelligence available to an attacker before an attack begins.
From hidden values to hidden relationships
Midnight’s model relies on several cryptographic components working together. Guillemot described note commitments, random secrets, zero-knowledge proofs, nullifiers and viewing keys as parts of a system designed to protect both transaction details and the relationships between users and assets.
The important distinction is between obscuring information with a predictable hash and preventing outsiders from linking an asset to its value or owner. A public hash may hide the contents of a record while leaving enough structure for observers to compare records, track movements or make educated guesses. A shielded design aims to make those connections unavailable without the information needed to open or verify them.
Under Midnight’s explanation, note commitments represent shielded assets without publishing their underlying details. Random secrets add unpredictability, while zero-knowledge proofs allow a user to demonstrate that a transaction is valid without exposing all of the information behind it. Nullifiers help prevent the same shielded note from being spent twice while avoiding the need to reveal the note’s full history.
The result is a different security posture from a transparent account model. An observer should not be able to build a complete balance profile, map an owner’s transaction history or easily identify which assets are associated with a particular participant.
Midnight’s official FAQ describes the related technical model, stating that commitments, nullifiers and zero-knowledge proofs are recorded on-chain, while private state, keys and proof inputs remain stored locally and encrypted. The FAQ also notes a practical tradeoff: if private state is lost, a user may be unable to access shielded notes.
That point is important because protocol-level privacy does not remove the need for reliable wallet infrastructure. The chain may protect information from public observers, but users still need to preserve the private material required to spend assets and generate proofs. Security therefore moves partly into wallet design, backup processes and key management.
Viewing keys create a controlled disclosure problem
Privacy is also not absolute in the sense that nobody can ever see anything. Viewing keys are intended to let an authorized party inspect relevant information without giving that party spending authority. They can be useful for accounting, compliance or payment monitoring, but they create a separate exposure point.
Guillemot warned that sharing viewing keys with third-party scanners can reveal incoming payment histories. That means a user who wants help locating or monitoring shielded activity may disclose more than expected. The transaction contents may remain hidden from the public, while the scanner gains a meaningful record of payments arriving at the wallet.
This is where the difference between confidentiality and control becomes practical. A viewing key can preserve some separation from spending authority, but it still grants visibility. Users must know what the key reveals, which party receives it and whether the recipient can combine that information with other identifying data.
The infrastructure question
The material supplied for this report contains one critical outside assessment, rather than a competing defense of Midnight’s approach. NightRiders argued in an article by Jesica Davis, reviewed by Jaromir Tesar, that wallet and indexer interactions can leak behavior. Its concern is that request timing, synchronization patterns and delegated scanning may expose information about users even when note contents remain encrypted.
That criticism shifts the focus from the ledger to the surrounding infrastructure. If a wallet repeatedly asks an indexer for updates, the timing and shape of those requests could reveal when a user is active or which private state the wallet is trying to recover. Delegating scanning to a service may improve convenience while creating another party capable of observing behavioral patterns.
Midnight’s structural privacy argument is strongest when it describes what outsiders cannot infer from the chain itself. It is less complete as a description of the entire user experience, which includes wallets, indexers, backup systems and viewing-key holders.
The conclusion depends on that boundary. Privacy can reduce attack surface by withholding the balance and ownership data that make profiling and targeted phishing easier. But the protection is only as strong as the systems that handle private state and authorized visibility. Midnight’s model will be judged not only by whether its proofs hide assets on-chain, but also by whether wallets can preserve that privacy while still helping users find, recover and monitor their funds.
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.