NØNOS Microkernel, track the release commits Live. We’ve begun pushing commits to the public GitHub, marking the release of the NØNOS microkernel. This is the beginning. Piece by piece, the vision becomes reality. Built with patience, purpose and love for what we’re creating.

See you in Buenos Aires at @EFDevcon The NØNOS team will be on the ground, meeting builders and researchers, also sharing our work on verifiable, zero-state system design.

We just published a full community statement on nønos, covering where the system stands, what’s coming next and why our mission is about verifiable privacy, not speculation. Read the full post: https://t.co/aTtNfRhEgT “Freedom begins when systems forget who you are.”

Solving Privacy at the System Layer with Deterministic Session Control We’re introducing a universal “Session Cleanup System” a practical, kernel-aligned solution to one of privacy’s oldest problems: application persistence. The problem is clear most privacy tools rely on

Did we find the first native wallet for @nonossystems for first distro release ? When you build an operating system from scratch, not a distro, not a sandbox but a deterministic, zero-state, cryptographically enforced microkernel, the first question for integrating a privacy

December 2025 remains our target for the first full release. The goal remains unchanged: an operating system that does not inherit trust, but proves its own integrity from the moment it starts. Nobody has been willing to rebuild digital privacy from first principles. Nobody

https://t.co/qKLSfKd8Cs

nønos-bootloader development update. The UEFI stage-0 bootloader for the NØNOS kernel is moving through its final architectural phase and the core of the system is now in place. The loader has been designed from the ground up as a zero-trust execution layer, responsible for

The market’s been rough, but that’s when the real builders shine. I’ve been digging into projects that are shipping, not just talking and this one caught my attention. Solid team, active community, and clear direction. 🔥 A verifiable OS, built from scratch. No Linux, no

{ noxorius }Development update. The latest cycle delivered a substantial refactor and a major tightening of the architecture. Core modules were reorganized, duplication removed and the dependency graph formalized into a clean hierarchy (types to core to security) with no

We will be hosting a community voice call on Telegram in approximately 30 minutes. 🔗 https://t.co/oAC43rxzXL This session will bring the development team and the community together to discuss nønos near-term direction, the broader vision and the principles that unify the

Hey fam, here’s a simple overview for everyone who joined recently and wants to understand what we are actually building. NØNOS is a new operating system built completely from scratch with one purpose: to create a computing environment that can be verified, not merely trusted.

@ethereum @EFDevcon @ethereum we’re building nønos, a cryptographic operating system written entirely from scratch, not forked, not layered. Every component, from the bootloader to the kernel, is designed for verifiable execution and zk-proof integrity at runtime. The goal isn’t just privacy, it’s

The works is progressing with our TUI now connected directly to the kernel through the KMI layer. It serves as the first visual interface to manage and test live kernel modules, starting with the cryptographic subsystem. Every crypto operation tested in the TUI runs through the

Thread giveaway, results. Winners of the two ZeroState Pass NFTs: @brander_kim - https://t.co/5BwELjtrXJ @Giacomo_CEO - https://t.co/2TndAibgUu Additional prizes: 5,000 $NOX each to @MFHUSSAIN618 @JohnnGfx @___Khonshu___ Winners: please reply with your ERC-20 address (DM us

The NØNOS TUI therefore represents the operational bridge between deterministic compilation and autonomous runtime verification. It is how the kernel proves itself before existing independently. Each screen, dashboard, build, run, Debug, crypto, system, logs and configs,

V) As development progresses, the NØNOS kernel transitions from being managed by a host process to executing as the host itself. Initially the kernel runs as a guest process invoked through QEMU, with the TUI managing build and runtime orchestration. Once the kernel reaches

IV) Build integrity, cryptographic validation and telemetry are unified within the log subsystem. Each log entry is time-stamped using monotonic counters and stored immutably for reproducibility analysis. Build histories, signature events and kernel outputs are deterministically

iii) The run interface instantiates the kernel in QEMU to allow isolated execution and live instrumentation. Kernel startup, interrupt handling and memory initialization are observed directly within this environment without exposing host resources. This sandbox allows tracing of

ii) The cryptographic subsystem defines the kernel internal trust boundary. All signing operations, module validations and build hashes are performed using (in first stage) Ed25519 within a locally managed key context. No external key material is imported at runtime; instead,

The nonos-kernel management interface (KMI-TUI) operates as a verifiable control environment for the NØNOS microkernel stack. It is not a front-end utility or debugging shell; it is a deterministic execution context designed to control, build and validate the kernel lifecycle