NØNOS is a trustless operating system built from the ground up in the Rust programming language, designed with a focus on security, privacy, and modularity. The system operates entirely in RAM and integrates anonymous networking capabilities through the Anyone SDK. ^[1]

Overview

NØNOS is presented as a new approach to operating system design, emphasizing a zero-trust security model. The project's core philosophy is that system infrastructure should be owned by its users rather than rented. It is being developed with a dual-layer architecture that combines cloud infrastructure management with a bootable, diskless environment known as ZeroState. This design aims to provide a high level of security by minimizing the attack surface and ensuring that no process can execute without cryptographic verification. ^[1]

The operating system is built entirely in Rust, a programming language known for its memory safety guarantees, which helps to eliminate common vulnerabilities like buffer overflows. All network traffic is routed through an encrypted mesh network, obscuring user IP addresses and providing device-authenticated communication. The system is also designed to be Web3-native, with built-in support for interacting with blockchain technologies like Ethereum without compromising the device's anonymity. Development is structured in a phased roadmap, with a public alpha release planned for 2026. ^[1]

Technology and Architecture

The NØNOS architecture is based on several core principles and components designed to work together to create a secure and private computing environment. ^[1]

Rust Microkernel

The foundation of NØNOS is a microkernel written entirely in Rust, containing no unsafe code blocks. This provides compile-time guarantees of memory safety, a critical feature for system security. The kernel employs a capability-based security model, where processes are granted specific, limited permissions, and all system calls (syscalls) are isolated and authenticated. This component serves as the cryptographic root of trust for the entire operating system. ^[1]

ZeroState Runtime

A key feature of NØNOS is its RAM-resident operation, referred to as ZeroState. The entire operating system, including all modules and runtime processes, is held exclusively in system memory. This diskless execution environment means that no data is written to persistent storage unless explicitly instructed. The system is designed to be bootable directly from UEFI firmware, loading the OS into RAM and managing its state there. This approach enhances security by ensuring that the system returns to a clean, verified state upon reboot. ^[1]

Anonymous Networking

All network communications from the NØNOS operating system are routed through the Anyone SDK. This integration provides access to an anonymous, encrypted mesh network. Communication is device-authenticated, and the system uses zero-knowledge proofs for identity verification, allowing for private interactions without exposing sensitive information like IP addresses. The routing is ephemeral, further enhancing user privacy. ^[1]

Modular Sandbox System

NØNOS uses a modular design for its applications and system components. Applications are packaged as sandboxed .mod binaries that run in isolated execution contexts. These modules communicate with each other and the kernel through secure Inter-Process Communication (IPC) channels. This architecture allows for the addition of new functionalities through pluggable kernel modules and applications without compromising the integrity of the core system. ^[1]

Development Roadmap

The development of NØNOS is organized into a multi-phase public roadmap.

• Phase 1 (Q2 2025, Completed): Research & Testing. This phase involved validating the architecture, prototyping the modular kernel, and conducting performance and security stress tests.
• Phase 2 (Q3 2025, In Progress): Core OS Foundation. Focuses on building the foundational Rust microkernel, including the memory-safe syscall dispatcher and the capability-based security model.
• Phase 3 (Q3/Q4 2025, In Progress): ZeroState & Bootloader. This phase involves implementing the UEFI bootloader and creating a fully bootable, diskless OS with persistent crypto-state management.
• Phase 4 (Q4 2025, Planned): Module System & IPC. Development of the sandboxed module system, secure IPC channels, and an advanced command-line interface (CLI).
• Phase 5 (Q3/Q4 2025, Planned): Anyone SDK Integration. This phase will integrate the anonymous networking protocol, zkProof identity system, and other Web3-native features.
• Phase 6 (Q2 2026, Planned): Production Release. The planned public alpha release, which will be accompanied by community testing programs, security audits, and developer documentation.

These phases outline a systematic progression from foundational research to a functional public release. ^[1]

Tokenomics ($N0NOS)

The NØNOS ecosystem is powered by its native utility and governance token, $N0NOS. The tokenomics are designed to support the protocol's development, incentivize participation, and facilitate governance. ^[1]

Token Launch and Supply

The $N0NOS token launch is planned as a two-phase process across two different blockchains to manage distribution and establish its economic model.

• Phase 1: Solana Launch: The initial launch took place on the Solana network via the Pump.fun platform, with an initial supply of 1,000,000,000 tokens. Following this launch, a supply reduction plan was initiated, using on-chain burn transactions to lower the total supply on Solana to a target of 690 million tokens.
• Phase 2: Ethereum Deployment: Once the 690 million supply cap is reached on Solana, the token will be deployed as an ERC-20 token on the Ethereum mainnet. The Ethereum version will have an identical supply cap and tokenomics structure, serving as the primary layer for governance and protocol treasury management.

The total fixed supply across all chains is capped at 690,000,000 $N0NOS. ^[1]

Token Distribution

On the Ethereum network, the 690 million token supply is allocated as follows :

• • Circulating Supply: 70%
• Reserve Wallet: 30%

The Reserve Wallet is further divided to support the ecosystem :

• • DAO Wallet: 10%
• Community Rewards: 10%
• Contributor Rewards: 10%

The project states that there are no reserved tokens for venture capital funding. Vesting schedules for developer allocations are managed by time-locked smart contracts. ^[1]

Token Utility

The $N0NOS token has several functions within the NØNOS ecosystem:

• Protocol Access: Users can stake $N0NOS to host encrypted relay infrastructure, publish verified modules to the public registry, and launch decentralized applications.
• Microservice Payments: The token is used for pay-per-use terminal services, such as encrypted messaging and private testnets with zero-knowledge verification.
• Contributor Incentives: Developers who contribute modules that are merged into the system can earn rewards from a dedicated Contributor Vault.
• Plugin Economy: Developers can publish modules with usage-based pricing, creating a marketplace for OS functionalities. A revenue-sharing model distributes 60% of the revenue to the developer and 40% to the protocol treasury. ^[1]

NFT Integration and Revenue Share

NØNOS has launched a limited-edition NFT collection that provides holders with specific benefits within the ecosystem. These benefits include eligibility for $N0NOS token airdrops, a share of revenue generated from protocol fees, and enhanced voting power in the governance system. The revenue-sharing mechanism for NFT holders is active. ^[1]

Governance

Governance of the NØNOS protocol is managed by the Builder DAO, a decentralized autonomous organization designed to empower contributors. The model is based on a Contributor Registry that tracks developers based on verifiable on-chain activity, such as code commits signed with GPG signatures, without requiring them to reveal their real-world identities.

Voting within the DAO uses a quadratic voting model, which aims to distribute influence more equitably than one-token-one-vote systems. A member's voting power can be boosted based on their level of contribution to the project. Proposals require a vote quorum and are executed via a multi-signature verification process.

"This governance model does not protect power — it distributes it. If you contribute, you own. If you build, you decide."