ethereum:0x0a26c80be4e060e688d7c23addb92cbb5d2c9eca
This is the security model behind why I’m bullish on $NOX.
NØNOS 0.9.3 is running Telegram under an explicit application policy.
The policy grants Telegram specific capabilities: WAYLAND, network access, and its own home directory.
Critically, it does not grant "EXEC"
When Telegram attempts to launch another program through "execve()", the kernel evaluates the request against Telegram’s policy and rejects it:
"refused execve: its policy does not grant EXEC"
The attempted program never executes and Telegram itself continues running. That is least privilege enforced at the kernel boundary.
This matters because application compromise shouldn't automatically become system compromise.
If an attacker gains execution inside an application, the security boundary can still restrict what that process is permitted to access, execute, and interact with.
That reduces the potential blast radius of a compromised application.
No permission prompt. No user decision. No assumption that installed software should be trusted with arbitrary execution. The policy says no, and the kernel enforces it.
That is a fundamentally different security posture:
Compromise ≠ unrestricted control
For crypto exchanges, engineering environments and other high value infrastructure, that matters.
Bullish on what $NOX is building.
$NOX delivers, now it’s your turn to enter
Replying to @nonossystems
@nonossystems just released a super cool new privacy feature for teams users: Nil (document encryption) 👀
That's exactly how a real world use case for zero-trust technology should look like. Privacy 2.0 in the era of web3.
$NOX is criminally undervalued !!!
$ETH $ZEC $NEAR
$NOX delivers privacy
While some paper hands choose to sell an asset as $NOX moments before we fly , I choose staking $NOX racking 10,000 coins every 48 hours , soon will be making $1000 every 48 hours .. @nonossystems
Massive updates are in ⬇️
MASSIVE $NOX UPDATE.
$NOX has integrated $ANYONE into NØNOS, so here's a simple breakdown of what the latest update actually means.
NØNOS says @AnyoneFDN is now running inside the OS as its own capsule alongside NYM, with users able to switch between them from the browser.
The key difference is how they approach privacy:
• @AnyoneFDN uses onion routing, sending traffic through multiple relays so different parts of the route see different pieces of the connection.
• NYM uses a mixnet, mixing, delaying and reordering traffic to make communication patterns harder to analyze.
ANYONE = protects the route
NYM = protects the pattern
@nonossystems puts both approaches into the same OS while keeping them isolated through its capsule system.
The ANYONE capsule gets only the capabilities it needs, including network access, crypto services and memory. NØNOS says it can't write to disk, so it can't simply create a permanent browsing record there.
The update also includes ANYONE circuits, .anyone onion services, private services, PoW, and TLS downgrade protection.
NØNOS says the integration was tested against the ANYONE reference code, actual servers and finally on a real machine.
So why is this bullish?
Because $NOX isn't just adding another network. It's showing how different privacy technologies can become native components of an operating system.
For $ANYONE, having its network integrated into another privacy focused OS gives its technology another environment where people can actually use it.
Different networks.
Different privacy models. One OS.
$NOX is up ~116% in 30 days.
The move comes while @nonossystems keeps shipping, with its operating system and Ethereum privacy layer both moving forward.
NØNOS is building an OS from scratch in Rust around one rule: trust nothing by default.
Processes run inside signed capsules. Memory is isolated. Permissions are explicit. Persistence can be disabled, and closing a session wipes the RAM.
The privileged core is kept deliberately small, with drivers, networking, the compositor and applications running outside it.
The team is also working on measured boot, TPM anchoring, formal verification and post-quantum signatures.
Public beta reached real hardware in July.
Then version 0.9.1 signed an Ethereum transaction from inside the OS, with the wallet capsule keeping the private key inside the system.
Now the other half of the project is starting to take shape.
NØNOS Shield is designed for private transfers settled directly on Ethereum L1.
The system uses STARK proofs with no trusted setup.
On Sept. 25-26, the team open-sourced the Shield contracts, including the pool, verifier and tests.
They also showed a private transfer using around 3.96M gas, down from 7.4M a week earlier.
200 private transfers were run across 80 Sepolia wallets.
The proofs leave the device over Tor, while the relayer cannot see the payment.
Public testnet and apps are targeted for October 1.
The token sits underneath both sides of the project.
$NOX is used for operator-node staking and micro-fees for capsule and network services.
It also has a defined tokenomic mechanism around trading.
Buy tax is 0%.
Sell tax is 3%, with 10% of the tax burned and 90% paired back into the NOX/WETH pool, with the LP burned.
So selling is designed to simultaneously add liquidity and remove some supply.
The numbers are still tiny.
Around $2.5M market cap.
Daily volume often only $8K-$10K.
That explains how a token can move 100%+ without needing a major exchange listing.
The product is still beta.
Some drivers and hardware support aren't finished. Production fleet tooling is still being built. Shield hasn't completed its audit.
And formal verification of parts of the kernel doesn't mean the entire system has been formally proven.
If October 1 brings a working public Shield release, the market gets a much better way to judge that thesis.
Until then, $NOX is still a ~$2.5M token attached to a very early product.
The next milestone is much more important than the 116% candle.
This is a huge step for the entire crypto community and beyond!
ethereum:0x0a26c80be4e060e688d7c23addb92cbb5d2c9eca @nonossystems
Take a moment to read and comprehend
We recorded a full private payment on @ethereum from start to finish, on an iPhone.
One account shields NOX into the pool, then pays 1,000 to a second account. The phone builds the proof by itself in 92 seconds, a relayer delivers it over @torproject and Ethereum settles it in a single transaction.
Watch what the chain gets and what it never learns.
🧵
ethereum:0x0a26c80be4e060e688d7c23addb92cbb5d2c9eca
Team 124
Connection Room
@nonossystems
What is NØNOS:
NØNOS is a zero-trust OS built from bare metal, a Rust microkernel that runs from memory and only runs signed software.
On top of it they build their own STARK proof system and NOX Shield, private transfers on Ethereum verified on chain in one transaction.
Complicated and quality tech that I respect and enjoy checking.
Welcome $NOX to my room
10
246
Great breakdown about $NOX project
I spent some time going through the new @nonossystems website. Honestly, it changes the way I look at the project.
This is no longer just about a secure OS.
NØNOS is building a security foundation for the next generation of connected devices. $NOX
We getting there …. It’s so early to enter now
ethereum:0x0a26c80be4e060e688d7c23addb92cbb5d2c9eca
This project is a $1B club member, wait and see
5 figure buy on $NOX. Still watching from the sidelines anon? @nonossystems will melt faces lol 😆
Worth noticing to $NOX updates 👀
Most stacks still assume the machine will remember everything and that’s the part that keeps breaking privacy in practice. What changed here is that the proof can sit on the same path as the code that actually executes, then the session can disappear. You’re not bolting privacy onto a system that was built to log. You’re proving the work and leaving almost nothing to reconstruct later.
That’s why this one is worth noticing. Not because it’s louder or we are louder. Because it fits how the rest of the OS was already being built.
$NOX is loading full send mode, don’t sleep on it .
This project belongs to the $1B club .
ethereum:0x0a26c80be4e060e688d7c23addb92cbb5d2c9eca | @nonossystems - Whale buys just came in 50% giga chad candle.
You sleeping still?
1
8
98
I never held on a project as much/long as I held $NOX , but with a team that never stop working and improving you can’t go wrong . If they can work relentlessly for a year , the least I can do is to support by holding and believing in the team .
When you have a diamond 💎 in your hand , be a diamond 💎 hand 👊 .
@nonossystems
Introducing the new nonos.software
The site was rebuilt so NØNOS can be understood by walking through it. The operating system proves what it runs before anything is allowed to execute and the homepage now follows that trust chain from power-on to a running program, one stage at a time.
Published with it are the full roadmap to v1.0, signed downloads with checksums and attestation bundles, in-browser verification, a redesigned NOX staking console, and pages for news, events, research and a community room that does not require an account.
🧵
ethereum:0x0a26c80be4e060e688d7c23addb92cbb5d2c9eca
This is big.
@nonossystems just published a public ~899 KB proof of a real shielded Ethereum transfer.
No trusted setup, no operator, STARK-based (post-quantum).
@eKnonos innovating.
$NOX to billions.
ethereum:0x0a26c80be4e060e688d7c23addb92cbb5d2c9eca
Bull case for $NOX
1st true Zero-Trust OS built from scratch in Rust
RAM-only, no disk traces, post-quantum crypto, ZK capsules, onion mesh
Privacy + sovereignty as the product, not a feature
Early infra live, tiny mcap, ready to send
Higher
Keyser Söze retweeted
NØNOS is proud to announce that our first beta release will launch between July 14 and July 22.
A microkernel written from nothing. Rust, bare metal, no inherited trust. Every program runs as a signed capsule that has to earn its place or it doesn't run at all.
The guarantees aren't adjectives since they're beings proven. Lean, Kani, Verus, against the code that actually ships and re-checked in CI on every commit. Reproduce them yourself.
Latest from the hardening bench 👇
medium.com/@nonos/the-state-…
Today we started the dedicated kernel-hardening branch and moved the benchmark pipeline into real evidence mode.
Latest CI artifact.
- boot evidence: pass
- build verifier: pass
- 45 capsule ZK attestations: ok
- ZK attestation failures: 0
- panic/fatal markers: 0
- kernel core ready: 114 ms
- microkernel init: 50 ms
- userspace entry: 2.85 s
- first capsule spawn: 116 ms
- first GPU transfer/scanout/flush: ~8.4-8.6 s
This is the standard we want: every claim moving toward logs, JSON, CSV, hashes, repeatable CI artifacts and hardening commits.
Kernel hardening today already started closing real boundaries: syscall authority, runtime capsule loading, IRQ grant cleanup, hardware support source evidence and raw memory reads routed through usercopy.
Get at: github.com/NON-OS/nonos-micr…
Infos covered at: github.com/NON-OS/nonos-micr…
1
298

























