Midnight’s roadmap says Passport SDK v1 is planned for the fourth quarter of 2026. The proposed SDK would enable account creation without seed phrases while allowing users to retain control of their data, identity and money. It would also support delegation to agents, a feature with clear implications for applications that can act or spend on a user’s behalf.
That makes Passport more than an onboarding tool. It is intended to connect Midnight’s privacy technology with ordinary account behavior: authentication, recovery, application permissions and identity proofs. The roadmap links the system to selective disclosure, allowing users to prove eligibility, authority or compliance without revealing information that is not needed for a particular interaction.
The distinction matters. A privacy network can shield transaction details, but applications still need ways to establish who is permitted to perform an action. A lending application may need to know that a user meets an eligibility requirement. A business workflow may need proof that a signer has authority. A regulated service may need a compliance credential. Selective disclosure aims to provide the proof without turning an entire identity record into a public or application-wide data dump.
Passport’s status is important here. The official Passport SDK README describes it as the user-facing identity and wallet layer for onboarding, authentication, scoped grants, recovery, storage, proving and decentralized application connectivity. But the same repository says the project remains at the planning and specification stage. Version 1 has been defined, yet no package has been released.
Midnight’s identity documentation explains that Passport is being developed as a passkey-based identity and account layer. Its design goals include scoped and revocable grants for decentralized applications, recovery and selective disclosure. The documentation also says that no published SDK exists yet and that the current demonstration is limited to Stagenet.
That gap separates the promise from the usable product. A roadmap can describe an account model, but developers will ultimately need stable interfaces, clear security boundaries and behavior that remains predictable across applications. Users will need to understand what a passkey controls, what recovery can restore, who can authorize a delegated action and whether a grant can actually be revoked.
The central tradeoff is convenience against sovereignty. Seed phrases are difficult for many users, but they provide a familiar crypto model of direct control. Replacing them with passkeys and recovery flows may make onboarding more accessible. It can also create new dependencies. Recovery might rely on devices, storage providers, trusted readers or bootstrap services. Delegation might simplify agent-based applications while expanding the number of parties that can influence an account.
The technical questions are already visible in the project discussion. Midnight collaborators Karmoola and Nicolas Di Prima wrote in Passport issue #167 about unresolved questions involving viewing-key onboarding, trusted reader or bootstrap models, independently enforced wallet-as-a-service device signing, storage independence and the limits of relying on decentralized application code conventions to enforce authority.
Those concerns go directly to the phrase “user control.” Control is not established merely because a user does not see a seed phrase. The relevant question is private from whom. If a recovery provider can reconstruct access, if a trusted reader can see information needed for onboarding, or if an application can interpret permissions more broadly than intended, the system may still expose important trust assumptions. The design has to make those assumptions visible and constrain them technically.
No opposing view was found in the supplied sources. The critical position comes from Karmoola and Di Prima’s issue discussion, while Midnight’s roadmap and documentation describe the intended benefits and architecture. That means the open questions should not be treated as proof that Passport is insecure. They are, however, the questions that will determine whether its privacy claims survive contact with real applications.
Passport could give Midnight a practical route from privacy infrastructure to usable identity. If it delivers scoped permissions, recoverability and selective disclosure without creating hidden custodians, it may make private identity feel ordinary. If convenience depends on trust that users cannot inspect or revoke, it could reproduce the surveillance and custody patterns that privacy networks are meant to avoid.
For now, Passport is a planned Q4 2026 release, not a shipped product. Its success will be measured less by the absence of seed phrases than by how clearly it preserves ownership, limits disclosure and defines who can act for the user.
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.