Badger retweeted
Good Morning,
We are post-0.9-beta and already closing hardening gaps in the open with proofs.
PR #405 aims 5 trusted-path fixes (frame aliasing, cross-capsule keylogging, IPC reply injection, service squat, framebuffer swap) each with a machine-checked Lean proof (0 sorry) + a runnable test.
If we can't prove it, we don't claim it.
github.com/NON-OS/nonos-micr…
Badger retweeted
Today, NØNOS ships its first public beta.
A Rust microkernel where every program proves itself before it runs, booting on real hardware into a full desktop. Signed, attested, verifiable from the bootloader up.
An honest beta, built in the open.
nonos.software/download/
(blake3 sums and the full attestation bundle are on the download page)
It is a beta and it is honest about being one. The foundation is strong and the edges are still rough. Our priority now is growing the driver base so more machines just work and we will do it in the open, one commit at a time.
Download it, boot it, and verify every claim against the source. Open an issue, send a boot log from your hardware, send a patch. We would be glad to build this with you.
Badger retweeted
Since input came up on real hardware, here's what's on the bench.
The touchpad and keyboard driving cleanly on a retail x86 laptop was the milestone that unlocked the rest and it proved the whole model works: signed userspace drivers, isolated, reaching hardware only through kernel broker grants, holding up on silicon the emulator never exercises.
Now while debugging continues we moving forward WiFi Stack.
The chip-independent half is done and proven as WPA2 four-way handshake, the scan/authenticate/associate MLME and the CCMP data plane that turns ethernet into encrypted 802.11 and back with the AAD and nonce checked byte-for-byte against the IEEE spec. A network name and a password go in one end; a scanned, authenticated, keyed, encrypting link comes out the other. Every stage has a known-answer host test.
Under that, the per-chip driver. We're bringing up a Realtek 802.11ac part: register access, the power-on table transcribed from the vendor's own values and the full firmware-download path header parse, section split, DMA transfer, checksum with all being validated against the real firmware image the card actually runs. The cold-start capsule compiles.
A note on how this is built. Vendor register values are hardware facts, so we reimplement fresh rather than copy, keeping the tree license-clean and every layer ships with a proof that runs on the host, no board required because it compiles is not it works.
What's left is honest: the RF calibration and on-silicon bring-up, the part that can only be tuned by booting the real card and measuring what it does. That's the road ahead and we're walking it in the open, one proven brick at a time.
Security-first is usually sold as giving up real hardware. We're building the counterexample.
(video below is a debug-kernel)
Want to get involved? DM the house 🫡
The isolated-driver input stack now runs on real laptops.
Every driver is a signed userspace capsule; hardware access only through kernel broker grants. That model now drives retail hardware end to end.
Covered today x86_64 on Intel Atom-class SoCs (Apollo Lake, Gemini Lake) with LPSS I2C support spanning Skylake through Meteor Lake platforms. HID-over-I2C precision touchpads, vendor-agnostic: PTP mode negotiation, palm rejection, adaptive acceleration. i8042 and EC-emulated PS/2 keyboards. xHCI USB HID. NVMe and AHCI storage. UEFI GOP display. Virtio for VMs.
Along the way, the first sustained 500 Hz input stream flushed out two scheduler-class kernel bugs no emulator ever hit. Fixed and now permanent regression surface.
Want your machine class next? Send us
* lspci -nn
the input lines of your dmesg and an ACPI table dump. Ports get prioritized by what the community actually runs.
Mission moving.
Badger retweeted
Read this slowly. This is not a marketing post. This is a manifesto.
The internet did not start this way. It started with permissionless access, self-custody and the radical idea that an individual could exist online without asking permission first. Somewhere along the way that got traded for convenience. Most people did not even notice the trade happening.
$NOX is built by a team that noticed.
No backdoors. No hidden control paths. No forced trust. Every process isolated. Every piece of software cryptographically signed before it runs. Zero persistent state by default. A kernel that verifies instead of assumes.
This is privacy as architecture, not privacy as a feature you toggle on.
What strikes me most is the honesty in how they frame it. This is not anti-anyone. It is pro-individual. It is the recognition that the moment people stop caring about their own sovereignty, control gets repackaged and sold back to them as convenience.
That is exactly what has been happening for the last decade across every platform we use.
@nonossystems is a quiet rejection of that direction. Built in the open. Pre-beta. No hype. Just architecture that holds up under scrutiny because it was built to be inspected from day one.
Privacy was never supposed to be a slogan. It was supposed to be defended.
NOX is doing the defending.
🤖 Made with AI
Privacy is not going to remain a niche topic.
It is going to become impossible to ignore.
Every year, more of the digital world is shaped around control: who can access, who can speak, who can build, who can transact, who can exist without being watched.
NØNOS exists because we refuse that direction.
We built this with a simple principle:
no backdoors, no hidden control paths, no forced trust.
Why ?
We must be inspectable.
We must be explicit.
Everything must be verifiable.
Users must remain sovereign.
This is not about being anti-anyone.
It is about refusing a future where people are reduced to permissions inside systems they do not own.
We say no.
We are willing to re-embrace the ideals that made Satoshi work matter in the first place.
The same principles that narrate Silk Road story.
Privacy. Self-custody. Open systems.
Permission-less access. No forced trust.
Those principles were not meant to become slogans.
They were meant to be defended.
The world needs privacy.
But it also needs truth.
It needs people willing to listen, to think, to question and to defend what still matters.
Privacy is not only a technical problem.
It is a human one.
Because when people stop caring about their own freedom, control becomes easy to sell as convenience.
NØNOS exists for those who still believe the individual is worth defending.
Badger retweeted
NØNOS now runs the #Rust ecosystem, unmodified and verified and here is where that stands.
We built a std platform layer for our x86_64-nonos target, with no compiler fork and no patched crates. It keys on the target vendor inside a pinned rust-src and is pulled in by build-std while covers stdout, a real heap, random, time, args, a filesystem client, sockets and threads.
On top of it, packages pulled straight from crates.io build and run untouched: serde_json, regex and base64 compiled for the target and executed on the kernel with checkable output on the serial console and ripgrep, the published binary, was built from its own source, verified and loaded. No crate source was changed.
Thread 🧵 ⬇️
Badger retweeted
The first operating system @ethereum will be able to verify.
This time not an app, not a wallet or not another chain.
It was time to change something.
A full OS, written from scratch in Rust, where no program runs until it proves itself and the proof checks out on Ethereum.
This is NØNOS today, following the roadmap in silence. It is real, it boots and we are deep in building it right now. 🧵👇
Badger retweeted
This is the most artfully constructed and well-planned humiliation I have ever seen.
Badger retweeted
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🧵
Badger retweeted
Today was a trusted-path hardening day.
We removed raw user-pointer dereferences from the syscall path and moved usercopy behind one access-aware page-table walker.
We tightened the kernel’s authority model around pcb.caps_bits, kept the syscall ABI native with tag4 IDs, hardened address-space teardown, added the boot handoff validation and gated capsule IPC port collisions.
On the JONOS side, we locked the production shape for capsule trust:
**NØNOS Trust Anchor** > **NØNOS ID Certificate** > **Capsule Manifest**
with a hybrid Ed25519 + ML-DSA-65 policy.
There’s still work before we call the trust chain complete, especially wiring verification into capsule spawn and proving it in boot but today removed real classes of mistakes from the kernel path.
Badger retweeted
We’ll be at @eth_milano
This will be the first time NØNOS is presented live not just as an idea, but as an existing evolving system.
We’ve been building a microkernel-based OS from scratch, where the goal is simple in words, hard in execution:
“an operating system that actually fits a decentralized, privacy-first environment, instead of adapting legacy models.”
At ETHMilan we’ll have:
- a 15-minute on-stage session
- a live walkthrough of the system and architecture decisions
- time to connect with people who care about systems, not just narratives
This is a step out of the “build in silence” phase and into real-world exposure and feedback.
If you’re around, come see it run.
Badger retweeted
Joe Rogan showing up to the White House after spending a month claiming to be politically homeless
Badger retweeted
It’s coming nicely <Ø>
NØNOS v0.8.4 arriving soon.
This release will mark the transition to microkernel architecture. Twelve services operating in isolated address spaces. Hardware-enforced boundaries between every component. Three-stage cryptographic boot verification.
Security through architectural isolation, not reactive patching.
Technical details: nonos.software/news/v084-rel…
Badger retweeted
🧵 NØNOS Bootloader
Added ZK replay protection to the boot attestation. Every proof is now bound to the kernel hash, a fresh boot nonce, the timestamp and a TPM-derived machine ID. A captured proof cannot be replayed on different hardware or a different boot session. Redesigned the UI with transparent cyan panels rendered directly over an embedded wallpaper.
Badger retweeted
Early testers are already running NØNOS across a range of environments from bare-metal hardware to virtualized setups such as Proxmox.
As expected for an alpha release, several early issues could be identified and now are being reported then tracked and addressed. This helps validating architecture and expanding hardware coverage through real-world testing.
If you’d like to contribute:
1) Run NØNOS on your hardware
2) Report findings or issues
3) Share feedback with the community
Issues: github.com/NON-OS/nonos-kern…
CI: github.com/NON-OS/nonos-kern…
Downloads: nonos.software/download/
Thank you to everyone already testing and helping move the project forward.
Badger retweeted
From zero traces comes absolute sovereignty, dream boldly, build relentlessly, and never let anyone tell you privacy is impossible.
#NØNOS #PrivacyByDesign #RustOS #DePIN
A year ago, i visualized an idea. It started as an extreme prototype, a simple React web viewer just to give shape to a vision, something visible to represent the end goal.
Then the real work began.
I hardened a Linux kernel. I spent months studying it deeply. Eventually understood something important: hardening alone would never achieve what expected and wanted. Reaching a true zero-state RAM-only system would require rethinking the kernel from the ground up and not because Linux isn’t the best kernel available today. It absolutely is but the goal here is different.
Linux is designed for persistence, compatibility and general-purpose computing. My goal is ephemeral computation and absolute minimization of traceability.
Hardening reduces attack surface.
It does not eliminate state and as long as state exists, it can be recovered.
That is the fundamental problem.
I want to protect $BTC or $ETH and the ideology behind crypto. I want protect my identity and people’s privacy uncompromisingly.
I don’t care about the mainstream Web3 narrative. Most of it has no real purpose. I’m not building hype.
It’s more about solving an enigma.
A real problem.
A problem that affects every so-called *solution* built on fragile guarantees, systems vulnerable to mathematical compromise, confiscation risk and forensic recovery.
Your *anonymous data* still lives somewhere.
Still sits on top of a kernel.
Still can be retrieved.
Still can be used against its operator.
STØP.
My data. My right.
My right is not a privilege.
Privacy is not a crime.
The real crime is losing control reaching a point where you can’t even look at yourself in the mirror because something that was yours is gone.
Everything I do comes from passion.
I’m building something I believe in. Something that takes time. Something that will evolve shaped by ideas, by feedback, by people who believe in the mission.
Today, NØNOS works on real hardware.
Multiple devices tested.
More to come.
The work continues.
As announced, we target 03.03.2026 for the full codebase release and the start of alpha testing.
They told it wasn’t possible.
I laughed.
If you can’t dream, you have nothing left.
Dreaming is stronger than opinion.
Never stop.
Many people supported this journey & their strength helped keep it alive.
I’m writing this because the feeling is incredible.
Most people chase money.
I’m chasing the excitement of building something meaningful.
Something special.
Something real.
One day i said: “From Ø, Sovereignty.”
Today we are at Ø.
Next comes sovereignty.
Long life to NØNOS.
Long life to the mission.
Badger retweeted
A year ago, i visualized an idea. It started as an extreme prototype, a simple React web viewer just to give shape to a vision, something visible to represent the end goal.
Then the real work began.
I hardened a Linux kernel. I spent months studying it deeply. Eventually understood something important: hardening alone would never achieve what expected and wanted. Reaching a true zero-state RAM-only system would require rethinking the kernel from the ground up and not because Linux isn’t the best kernel available today. It absolutely is but the goal here is different.
Linux is designed for persistence, compatibility and general-purpose computing. My goal is ephemeral computation and absolute minimization of traceability.
Hardening reduces attack surface.
It does not eliminate state and as long as state exists, it can be recovered.
That is the fundamental problem.
I want to protect $BTC or $ETH and the ideology behind crypto. I want protect my identity and people’s privacy uncompromisingly.
I don’t care about the mainstream Web3 narrative. Most of it has no real purpose. I’m not building hype.
It’s more about solving an enigma.
A real problem.
A problem that affects every so-called *solution* built on fragile guarantees, systems vulnerable to mathematical compromise, confiscation risk and forensic recovery.
Your *anonymous data* still lives somewhere.
Still sits on top of a kernel.
Still can be retrieved.
Still can be used against its operator.
STØP.
My data. My right.
My right is not a privilege.
Privacy is not a crime.
The real crime is losing control reaching a point where you can’t even look at yourself in the mirror because something that was yours is gone.
Everything I do comes from passion.
I’m building something I believe in. Something that takes time. Something that will evolve shaped by ideas, by feedback, by people who believe in the mission.
Today, NØNOS works on real hardware.
Multiple devices tested.
More to come.
The work continues.
As announced, we target 03.03.2026 for the full codebase release and the start of alpha testing.
They told it wasn’t possible.
I laughed.
If you can’t dream, you have nothing left.
Dreaming is stronger than opinion.
Never stop.
Many people supported this journey & their strength helped keep it alive.
I’m writing this because the feeling is incredible.
Most people chase money.
I’m chasing the excitement of building something meaningful.
Something special.
Something real.
One day i said: “From Ø, Sovereignty.”
Today we are at Ø.
Next comes sovereignty.
Long life to NØNOS.
Long life to the mission.
Badger retweeted
A powerful reminder: true privacy isn't just coming back—it's being rebuilt from first principles. Excited to see
@nonossystems
leading the charge with NØNOS. The future looks sovereign.
#privacy #Nox
Badger retweeted
Salam Gent,
A very personal note what the app actually is and why we built it this way.
What sucks ? Privacy browsers are either 150MB Chromium forks or browser extensions that can be bypassed. Most just route traffic through Tor and call it done.
What we built:
i) Lightweight native app (~8MB) Tauri + Rust. Uses system webview for rendering but all network requests go through our proxy first. The webview never touches the internet directly.
ii) Application-level security has WebRTC blocked. WebSocket blocked. Service Workers blocked. sendBeacon blocked. All JS overrides frozen so sites can't bypass them. SSRF protection. Meta refresh rewriting.
This approach make security happens in compiled Rust before anything reaches the renderer.
iii) Anyone Network routing. Decentralized relay network with community-run nodes. Multi-hop encrypted routing.
## The daemon (in progress) This is where it gets different:
a) Request pooling batches requests before sending
b) Timing jitter so random delays break correlation
c) Fisher-Yates shuffle randomizes request order
* Encrypted cache with Poseidon commitments * Merkle tree for ZK proofs
## Mix network architecture. You can't analyze timing. You can't read the cache. You can't prove what was accessed.
## Why it's different:
Tor routes traffic. We mix it.
Tor Browser is 100MB+. We're 8MB.
Extensions can be bypassed. Rust can't.