Safe & secure NONOS wallet
Take control of your NONOS assets with complete confidence in the Trezor ecosystem.
- Secured by your hardware wallet
- Use with compatible hot wallets
- Trusted by over 2 million customers
Send & receive your NONOS with the Trezor Suite app
Send & receive
Trezor hardware wallets that support NONOS
Sync your Trezor with wallet apps
Manage your NONOS with your Trezor hardware wallet synced with several wallet apps.
Trezor Suite
MetaMask
Rabby
Supported NONOS Network
Why a hardware wallet?
Go offline with Trezor
- You own 100% of your coins
- Your wallet is 100% safe offline
- Your data is 100% anonymous
- Your coins aren’t tied to any company
Online exchanges
- If an exchange fails, you lose your coins
- Exchanges are targets for hackers
- Your personal data may be exposed
- You don’t truly own your coins
How to NOX on Trezor
Connect your Trezor
Open a third-party wallet app
Manage your assets
Make the most of your NOX
Trezor keeps your NOX secure
Protected by Secure ElementThe best defense against both online and offline threats
Your tokens, your controlAbsolute control of every transaction with on-device confirmation
Security starts with open-sourceTransparent wallet design makes your Trezor better and safer
Clear & simple wallet backupRecover access to your digital assets with a new backup standard
Confidence from day onePackaging & device security seals protect your Trezor’s integrity
NØNOS is an operating system built around privacy at the level of the kernel. Its design position is that a program is owed nothing and receives only what it has been explicitly granted.
The kernel is a microkernel with capability-based security. The component that grants and checks authority is under four thousand lines and is formally verified: the Rust is translated into Lean 4 by Charon and Aeneas, and the model is machine-checked to refine the extracted code, so the theorem covers the capability system as it ships.
Every program runs as a capsule, signed and started with exactly the permissions declared in its manifest, checked at spawn against the ceiling carried in its certificate. A capsule granted no network capability has no route to the network, no interface through which to request one, and no consent dialog through which a user can be persuaded to provide one. There is no root account and no administrator, so there is no authority to escalate toward.
Device drivers, the TCP/IP stack, the display server, the browser and the wallet/apps all run as capsules outside the kernel. Roughly 600k + lines of the system hold no privilege and have no path into the kernel address space.
The system is RAM-resident. After shutdown no logs, caches, browsing history or device identity remain on the machine. Network traffic leaves through an onion mixnet implemented inside the kernel with a fresh key agreement at every hop. Nothing executes unproved. The bootloader verifies the kernel under two independent signature schemes, one of them post-quantum, then checks the kernel own STARK proof against a root compiled into the bootloader. Each capsules proof is verified before its image is mapped, and a missing or invalid proof means the capsule does not run. The proving system is the project own transparent STARK over the Goldilocks field, requiring no trusted setup and no pairing-based cryptography. That same prover settles NOX Shield, a private transfer protocol verified on Ethereum by a Solidity contract. NOX is the ecosystem ERC-20 token on Ethereum.