Shielded by design
Onuros is built for private payments, with cryptographic proof verification at the protocol boundary.
Financial privacy starts here
The world's
fully shielded
cryptocurrency.
Private payments. A compact 248-byte format. Powered by proof of work.
The Onuros idea
Privacy in every layer.
Your keys. Your control.
Create an encrypted local wallet with a 24-word recovery phrase. Disclosure remains under the wallet owner’s control.
Independently verified
Miners submit work. Nodes independently check the proof before admitting a completed block.
Compact by design
OCWF-248 defines a canonical 248-byte payment format shared across the Onuros stack.
Authenticated connections
Wallet and mining services use authenticated TLS connections with network identity checks.
One connected system
Protocol, node, wallet and miner each have a focused role in the same private-payment network.
Conceptual animation · not live network data
Current scale
Compact today.
Pushing further tomorrow.
248 bytes per payment. Current capacity approaches 6,000 payments per block—roughly 100 TPS at the 60-second target interval. In the upcoming public testnet, we'll put that capacity to the test and push for more.
Shielded by design
Your payment stays private.
Its validity is proven.
OCWF-248 is Onuros's custom 248-byte payment format. Zero-knowledge proofs let the network verify payment rules without revealing private payment details. Strict encoding and checks against double-spending make privacy and verification part of the same system.
Privacy is personal
Move your money.
Keep your life to yourself.
Your payments shouldn't tell your story. Onuros Wallet pairs encrypted local keys with shielded transactions, so the network can verify a payment without seeing its private details. You authorize the spend. Cryptographic proofs establish validity. Independent checks stand against double-spending.
Your keys. Your money. Your business.
Protocol
Small format.
Clear rules.
OCWF-248 defines a canonical 248-byte payment format. Proof verification and strict encoding provide a shared foundation for the Onuros stack.
Explore the protocol ↗Build with Onuros
Bring your expertise.
Help shape what's next.
Stay close to what comes next
The future is private.
Build it with us.
Ecosystem
Your way into Onuros.
Onuros Wallet
Your keys.
Your private world.
Create, restore and open encrypted local wallets with a 24-word recovery phrase. Windows and Linux desktop packages are qualification candidates.
Live balances and payments require a qualified synchronized backend. These builds are not production ready.
Onuros Miner
Put your hardware
to work.
Native KawPoW mining with optional NVIDIA CUDA. Host-side candidate checks and authenticated node connections are built into the work flow.
A compatible development node is required. Candidate artifacts and source-build instructions are available in the repository.
Repository access may be required for documentation and qualification downloads.
Network
Explore the Onuros network.
Status, chain exploration and pool access in one place.
Onuros Status
Network health, availability and service updates.
Live monitoring not connectedVisit status.onuros.com ↗Onuros Explorer
A destination for public block and transaction information.
Endpoint availability unverifiedVisit explore.onuros.com ↗Onuros Pool
A destination for pool information and mining activity.
Endpoint availability unverifiedVisit pool.onuros.com ↗The service addresses could not be verified and may be unavailable. For help, contact help@onuros.com.
Documentation
Understand. Build. Verify.
The current guides and complete documentation folders for all four Onuros components.
Onuros Protocol
Protocol documentation
Browse all protocol documentation ↗Onuros Node
Node documentation
- Node overview
- Mining and requirements
- Daemon interface
- Mining protocol
- Runtime boundaries
- Validation evidence
Onuros Wallet
Wallet documentation
Browse all wallet documentation ↗Onuros Miner
Miner documentation
- Setup and commands
- GPU operation
- Node wire contract
- Live mining transport
- Operator guide
- Hardware evidence
Documentation follows the current source repositories. GitHub access may be required.