Pinned Tweet
$ZEC and $XMR were the first to take our privacy rights on chain
Now $NOX is building on that same mission, just at a different layer of the stack.
let’s dive in
@nonossystems
1/7
The next stage of NØNOS: Implementation of the deterministic attestation and verification layer.
As the bootloader moves towards v0.1 completion, focus moves to embedding the cryptographic verification path directly inside the initialization chain. The objective is a fully self-contained execution environment where proof verification, circuit integrity and provenance exist at the firmware boundary and before any dynamic subsystem runs.
The new contributor-driven workflow enables external developers to create and verify circuits that extend the attestation layer. Each contribution includes reproducible build instructions, verifying keys (VKs), metadata and optional zk-ceremony transcripts for Groth16 setups.
Our deterministic CI replays each circuit build in a hermetic sandbox, ensuring byte-for-byte reproducibility of the VK. The CI also generates a reference proof to confirm functional validity. Once validated, the VK is compressed, hashed and serialized through zk-embed, producing a canonical Rust snippet containing:
i) PROGRAM_HASH constant (domain-separated by namespace)
ii) normalized compressed VK bytes
iii) a lookup function that binds the proof program to its verifier
That snippet is compiled into the bootloader, producing an image that embeds a verifiable registry of circuits, every verifier linked to its exact source and ceremony transcript. At runtime, devices can verify proofs entirely offline, using embedded VKs with no external fetches, no trust in remote servers and no mutable key sources. Each build of the bootloader is a cryptographic snapshot of trust, deterministically reproducible by any third party.
Security mechanisms are being extended to handle revocation of compromised VKs through signed capsule updates and memory-safe deprecation lists at boot. On constrained systems, proof verification can be delegated to companion secure elements via a future co-processor handshake protocol, while maintaining deterministic attestations at the kernel boundary.
The reward layer begins with verified merge bounties deterministic payouts triggered on successful CI validation and maintainer review and evolves into usage-based and maintenance incentives that measure actual proof activity in the field.
The NØNOS bootloader thus becomes the first stage in a self-contained trust pipeline:
source > reproducible verifier > compiled boot image > hardware-level validation.
This is what decentralization looks like when engineered at the silicon boundary not in contracts, but in the boot chain itself.
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.
Big dog put a couple Billies in his pocket first, then janked the ladder
how convenient
History will remember this as the moment a president chose a higher standard of ethics than the law required of him. This agreement bans ALL federal officials — including the President — from issuing or sponsoring a digital asset for profit, with real enforcement and real penalties.
Thank you, @POTUS! Let's get the Clarity Act passed NOW.
Readers added context they thought people might want to know
President Trump and First Lady Melania Trump previously launched the $TRUMP and $MELANIA meme coins, which generated substantial revenue for Trump-affiliated entities and prompted bipartisan ethics concerns over public officials profiting from digital assets.
abcnews.go.com/Politics/trump…
48
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.
let me translate this for you:
every cent spent on compliance will be extracted from users 100x
~Teng
@binance xitter.cf/_richardteng/status/20…
2
328
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.
people miss the fact that if elmo actually showed a drop of decency and tried to use his money to help the masses he would be disposed like a wet rag at a whorehouse
he’s allowed to be who he is but he doesn’t truly controls his money
change my mind
30
look at these fucking guys
inspired by a gov honey pot
5 minutes of research will show you better actual private networks and Operating systems like $ANyONE and $NOX
then they wonder why people hate on $ETH
good job dorks!
Ethereum is inspired by tools that keep the internet open under pressure.
@torproject protects freedom online by routing traffic through distributed relays, reducing tracking, surveillance, and censorship.
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 🧵 ⬇️
NØNOS sets you free
$NOX
The US government, citing national security authorities, has issued an export control directive to suspend all access to Fable 5 and Mythos 5 by any foreign national, whether inside or outside the United States, including foreign national Anthropic employees.
The net effect of this order is that we must abruptly disable Fable 5 and Mythos 5 for all our customers to ensure compliance.
Access to all other Claude models is not affected.
We apologize for this disruption to our customers. We believe this is a misunderstanding and are working to restore access as soon as possible.
Read our full statement: anthropic.com/news/fable-myt…
1
80
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. 🧵👇
it’s a different game when you play with other people’s money
regular folk jump out of windows when they lose a fraction of this
2
59
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🧵
NØNOS getting close to Beta!
have a read!
$NOX
@nonossystems
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 🧵
4
221