Adam Found

@BarrySilbert Ø is coming 🤜🏻

NØNOS loading for another week. Capsule manifests, NONOS-ID certificates, payload hashes, signing pipeline. One thing that already makes NØNOS different is that the architecture is not treated as a layer on top but it’s part of the runtime itself.

ETHMilan was honestly a great experience for us. It opened our minds in many ways as brainstorming, meeting new people and speaking publicly about NØNOS for the first time in front of a completely new audience. Those moments stay with you and become part of the journey while building something from zero. At the same time, development keeps moving. The roadmap is still ongoing and we’re currently targeting a beta release in roughly ±40 days if things continue progressing correctly. We’ll keep building quietly and consistently like we always have. A lot of the work happens in the dark long before people notice it publicly but commitment compounds over time. Appreciate everyone following and supporting the vision. By our founders.

@mattdotfi @rogermoonCrypto @eth_milano hey @mattdotfi One of the founders of $NOX @nonossystems called @eKnonos is speaking at @eth_milano tomorrow 🔥🤝 Check out this privacy monster in the making ⚡️🤓 They also have ties with $ANYONE @AnyoneFDN through community members etc 🌎

@DanaShostak GM🙌🏻

GM🌿

$NOX @nonossystems will show the world how your privacy matter 💎

@nonossystems is heading to @eth_milano 2026. May 21–22, Museo Nazionale Scienza e Tecnologia, Milano. Our Founders will be on the Main Stage to talk about what we are building. No disk. No assumptions. Just code you can verify. See you in Milan.

NØNOS reached a new integration point today. The desktop system graph now builds as one signed profile and is admitted under QEMU by the verified capsule loader. This is the first serious line between capsules compile and the OS graph boots together. A thread 🧵

In, exit, farm and bye. Meanwhile @nonossystems is here to stay🤜🏻

Today's work moved the OS closer to the public roadmap capsule-first hardware model: the kernel stays a verifier, scheduler, broker and IPC substrate; device logic and protocol policy continue moving into signed userland capsules. The milestone today is not saying, we finished networking or we finished USB. The milestone is that several critical paths are now past architecture-only work and into buildable, signed, statically gated integration. A thread🧵

NØNOS is moving multi-arch. Today on main: NØNOS, the capability-token microkernel we’ve been building, runs as a multi-architecture substrate. x86_64 stays the production lane unchanged bit-identical. The aarch64 (GICv3 distributor/redistributor + ICC, PSCI for CPU bring-up, CNTP timer, EL2 > EL1 drop) and riscv64 (PLIC, SBI Base/HSM/RFENCE/TIME/IPI, Sv39 paging, sscratch swap for U-mode trap) come up as parallel backends behind a single Arch trait. github.com/NON-OS/nonos-m…

We are past the alpha-kernel stage and deep into the part that matters: turning the architecture into an enforceable system. Current focus: capsule-native userland, signed trust chain, driver/service migration and real capability-token authority. What is already real: <>native NONOS syscall ABI, isolated address spaces, checked usercopy, IPC routing, ring-3 capsules, RAM-first services and signed capsule artifacts. <> The trust chain is now a serious milestone with already 13 capsule artifacts verify against the baked policy with NØNOS-ID certs, manifests, Ed25519 and ML-DSA-65. Both signatures are required. Active emerging capsule surface includes ramfs, vfs, keyring, entropy, crypto, market, proof_io, virtio-rng, virtio-blk, virtio-net, PS/2 input, xHCI and e1000. A thread 🧵

$NOX Staking V4 is live. nonos.software/staking A thread 🧵 This upgrade moves NOX staking beyond a simple deposit-and-reward contract. V4 is the base layer for stake-backed operator identity inside the NØNOS ecosystem.

NØNOS latest article is live. A concise update on the OS work: bootloader handoff, real assembly at the architecture boundary, kernel memory contract, userland capsules and the proof gates ahead. Read the article, then watch the engineering recap: x.com/nonossystems/s…

NØNOS & 0xNOX are entering its first real integration phase. SwapNox is live 0xnox.com/swap Bridge is live. 0xnox.com/bridge Docs are available. 0xnox.com/docs Publisher onboarding starts now. The next step is preparing serious privacy projects for the capsule-app model. We are open for collaboration and that’s what web3 should be. A thread 🧵 👇

|| Day 2/60 of NØNOS-Roadmap || Merged 5 exit paths towards 1 [] MkExit leaking pages + kstacks [] sys_exit leaking broker grants [] OneSignal kill leaking all Now [v] Single teardown for all Found a kstack UAF that would triple-fault on first MkExit. [v] Fixed: per-CPU pending-free queue (timer trap drained) Free only on owning CPU & cross-CPU = UAF once SMP is up Capsule faults fixed: Before: CPL=3 fault now halt CPU Now: teardown then reschedule Bad capsule dies alone, Ø life. Some Smokes-test could start tomorrow.

@DanaShostak Mistakes is a part of perfection

you were born to make mistakes, not to fake perfection

Today we started the first phase from yesterday announced nonos.software/roadmap This is the part where NØNOS stops treating the kernel as the place where every subsystem goes. The kernel is being forced into its real job: isolation, scheduling, memory, IPC, capabilities, capsule loading and hardware authority. A thread 🧵 ⬇️

$NOX @nonossystems let’s begin new era of internet privacy 💎