News
What shipped, and what it proves.
Announcements and updates from the project, written the way the releases are: what is true now, what changed, and how to check it.
Latest · 8 August 2026
NØNOS 0.9.1
410 commits since 0.9. The TPM spoken to directly, dual Ed25519 and ML-DSA-65 signatures, per-capsule STARK attestation, memory wiped before shutdown with a proof, four trusted-path faults fixed in Lean, Wi-Fi working on real hardware, and the reproducibility position stated precisely.
Read it8 August 2026
NØNOS 0.9.1
410 commits since 0.9. The TPM spoken to directly, dual Ed25519 and ML-DSA-65 signatures, per-capsule STARK attestation, memory wiped before shutdown with a proof, four trusted-path faults fixed in Lean, Wi-Fi working on real hardware, and the reproducibility position stated precisely.
Read7 August 2026
The first transaction signed inside the operating system
NØNOS 0.9.1 settled a transfer on Ethereum mainnet, signed by a wallet capsule that holds no signing library and never releases the key. The transaction is on chain and you can check every claim about it yourself.
Read28 July 2026
A place to build this together
The NØNOS community is now on Discord. A place to boot the beta, report from real hardware, and grow the driver base in the open.
Read17 July 2026
Attestation reaches the kernel
NØNOS now proves both the kernel and every capsule with a transparent, post-quantum STARK, checked by one shared verifier and four independent proof tools, and wired into a new configurable build.
Read17 July 2026
From radio silence to a real IP: bringing up WiFi on NØNOS
A sovereign operating system brought its own 802.11 stack up on a consumer laptop, from a ring-3 driver capsule to a DHCP lease, and every layer is ours and capability-gated. Here is exactly how, including the hardware quirk that nearly stopped it.
Read16 July 2026
NØNOS 1.0 launches July 22
Version 1.0 of the sovereign operating system ships July 22, 2026: a verified, RAM-resident OS where every program proves itself before it runs. Boot it live, read the full docs, verify every claim.
Read