Start mining.
Know every step.

01. Start here: what you are setting up

Mining is the process of using your computer to search for valid proof-of-work solutions. Onuros uses KawPoW. Your graphics card searches, the miner checks each candidate on the CPU, and the connected node verifies submitted work before accepting it.

You need four things: a suitable computer, a working graphics driver, an Onuros miner package with the correct engine, and access to a compatible mining service. You also need a wallet receiving destination for rewards. Installing a wallet alone does not start mining, and running a benchmark does not earn coins.

This guide starts with a PC that has no Onuros software installed. Work through the steps in order. Never enter your 24-word recovery phrase, wallet password or spending key into the miner.

02. Check your computer

Start with one graphics card and conservative settings. A larger rig adds driver, memory, power and service-connection requirements; it does not automatically make configuration easier.

The initial epoch DAG is approximately 1 GiB, with additional memory needed for cache, display use, driver components and temporary work. Later epochs can increase requirements. A 2 GiB card may have little headroom even if it is detected.

NVIDIA CUDA is the native GPU engine in the documented miner. Native AMD/OpenCL mining is not implemented in that revision. External AMD qualification tools are a separate path, not a ready-to-use AMD desktop release. Do not assume another KawPoW miner supports Onuros simply because it supports the same algorithm.

03. Install and check your graphics driver

Windows

1. Identify your graphics card in Device Manager or your PC's system information.
2. Download the appropriate driver through NVIDIA's official driver service or your computer manufacturer's supported channel.
3. Install it, restart if requested, and confirm the card is listed without a device error.
4. Open a terminal and run nvidia-smi if available. It should identify the GPU and driver. A missing command alone is not a complete hardware diagnosis.

Linux

Use your distribution's supported NVIDIA installation method for your exact GPU and OS version. Restart if required. Run nvidia-smi to check whether the driver sees the card. Do not copy installation instructions for a different Ubuntu version without checking compatibility.

Windows Subsystem for Linux

WSL uses the Windows NVIDIA driver. Do not install a Linux display driver inside WSL. If you are compiling CUDA software, use the Toolkit intended for WSL and follow its supported installation instructions.

A driver and the CUDA Toolkit are different components. A compatible packaged app may include or specify runtime dependencies; building the GPU engine from source requires the Toolkit compiler as well. The CUDA version printed by nvidia-smi is not proof that the compiler is installed.

04. Set up your reward wallet first

1. Install the official Onuros Wallet for the network you intend to use.
2. Create or restore your wallet, save your 24-word recovery phrase offline, and protect it with a unique password.
3. Use the wallet's verified receiving-address workflow when available in your release.
4. Confirm that the reward destination configured by your node or pool belongs to that wallet and the same network.

Follow the Wallet Guide for recovery, backups and mining reward maturity. Your miner needs an authorized mining connection; it does not need control of the wallet's private keys.

The documented native miner has no wallet-address command-line argument. The node or coordinator determines the reward recipient. An accepted solution does not prove that the operator configured your address correctly. Verify the payout destination before starting.

05. Choose the right miner download

Open the Onuros Ecosystem page and use the official miner download route. Read the package notes for your operating system, GPU engine and network. Avoid copied download links from unsolicited messages.

A Windows archive, a Linux archive and a desktop console are not interchangeable. Keep the app and its companion files together. A package carrying the Onuros name can still contain only the CPU reference engine.

If checksums are supplied, calculate the downloaded file's SHA-256 hash and compare the complete value. Windows PowerShell provides Get-FileHash -Algorithm SHA256; Linux provides sha256sum. A checksum checks the file against the published value, not the trustworthiness of an unknown publisher.

Do not disable all antivirus protection to install a miner. Confirm the origin, package integrity and release instructions before handling a warning. A qualification package should not be treated as an independently audited production release.

06. Install on Windows or Linux

Windows package

1. Download the package intended for Windows and your GPU engine.
2. Extract the entire archive into a folder you control. Do not run an executable from inside the compressed archive.
3. Keep the desktop console, native miner and supplied runtime files in the layout used by the package. The desktop console launches a companion miner executable.
4. Install only the runtime dependencies specified by that release. Do not download individual missing DLL files from unofficial sites.
5. Launch the desktop app if included. A command-line-only archive will not create a desktop console by itself.

Linux package

1. Choose the Linux x86-64 package matching your release and environment.
2. Extract it into a private application folder and keep its included files together.
3. Follow the package's launch instructions and install its documented dependencies through your distribution's package manager.
4. Use a regular user account for mining. Routine operation should not require giving the miner unrestricted root access.

If a download is unavailable or only a CPU candidate is offered, stop here and request the appropriate CUDA package through official support. There is no valid install command that turns an unavailable package into a published GPU release.

Source compilation is an advanced alternative. It requires compatible C++20, CMake, OpenSSL, paired node sources and a CUDA Toolkit/compiler combination. A clean PC should not be told that installing a driver is enough to compile the miner. Ask for instructions specific to your OS, GPU and exact release.

07. Check the engine before connecting

Use the native miner's local diagnostics before running a long session. Open a terminal in the executable's folder. On Linux, prefix an executable in that folder with ./; on Windows PowerShell use .\ and the actual executable filename.

• onuros-miner version shows the installed version and compiled capabilities. Look for gpu-engines=cuda for NVIDIA GPU execution.
• onuros-miner devices lists available backend devices and their indices.
• onuros-miner self-test --backend cuda --device 0 checks the selected CUDA device. Replace 0 with the index listed for your intended card.
• onuros-miner benchmark --backend cuda --device 0 --duration 10 performs a short offline speed check.

These commands are local checks. They do not require a wallet phrase and do not earn rewards. A CPU self-test does not validate a GPU engine. Device detection alone does not prove the device has passed physical qualification.

If the version reports the engine as unavailable, get the correct binary. If the GPU self-test fails, resolve the driver, runtime, memory or hardware problem before attempting live mining. The miner does not silently switch from a failed GPU engine to CPU mining.

08. Choose solo mining or a pool

Solo mining

Solo mining uses a node configured with your reward destination. The node assembles jobs and verifies blocks; the miner searches for solutions. The node and miner are separate programs even when installed on the same PC.

Finding a valid block is probabilistic. Running for a certain number of minutes does not guarantee a reward. A network's expected block interval is not your individual payout schedule. Running a full node adds storage, memory and maintenance requirements beyond this miner-only guide.

Pool mining

A pool combines participants' work and applies its own share accounting and payout rules. Before joining, check supported software, credentials, fees, minimum payout, payout schedule and the destination address recorded for you.

The documented native revision connects through the authenticated Onuros mining protocol. It does not implement ordinary Stratum wallet/worker flags. A compatible coordinator must provide the supported connection and define how your work is credited. Do not paste a generic Stratum URL into this build.

A website link or a pool name is not evidence that a compatible public service is active. Confirm availability through the Onuros Network page or official support before configuring a session.

09. Configure the mining connection

Obtain connection details through the official operator or a trusted compatible coordinator. The current native connection requires a dedicated mining endpoint, network identity, protected authentication-token file and TLS fingerprint file. Wallet RPC, explorer URLs and the mining listener are different services.

The desktop console provides fields for backend, device, node and network identity, plus Choose token… and Choose fingerprint… file selectors. Use the values supplied for your exact package and network. Where a newer package supplies a profile, follow that package's profile instructions instead of translating unrelated settings by guesswork.

The documented native CLI accepts a numeric IPv4 address and port, not a website hostname, an https:// address or a stratum:// URL. A prefilled field is not proof that a service exists or that its value is accepted by the companion engine. Do not assume a default mining port.

Keep authentication files private. On Linux they must belong to the mining user, be ordinary files rather than symlinks, and have owner-only permissions. Do not generate a random replacement token: it must match the operator's authorization.

Never disable certificate checks to work around a connection error. Check your PC clock, the supplied fingerprint and the operator's current configuration. No mining configuration requires your recovery phrase.

10. Start, monitor and stop mining

1. Close other GPU-heavy applications and ensure your cooling is working.
2. Select CUDA for NVIDIA GPU mining and the correct device index. CPU reference mode is a separate choice.
3. Review the supplied endpoint, network identity and credential files.
4. In a package with the desktop console, select Start. Keep the companion miner in the expected folder.
5. Read the native output for authentication, mining, hashing and accepted responses. A running animation or a state label alone does not prove acceptance.
6. Watch temperature, power and stability during the first session. Stop if the hardware reports errors or exceeds its manufacturer's limits.

The current desktop console starts a child process and displays its output. Some summary metrics are not automatically populated from that output in the reviewed implementation. Treat the actual engine responses as the evidence for acceptance, not an attractive dashboard counter.

Use Stop in the desktop console. In a foreground terminal, use Ctrl+C and wait for shutdown. Avoid launching a second copy before the first stops. Closing your laptop lid, suspending the PC or losing network access interrupts work.

11. Read the mining results correctly

An increasing accepted counter and successful native response indicate accepted work. That counter is local to the running process. It can restart at zero when the miner restarts; this does not by itself mean previously recorded chain rewards disappeared.

Accepted count is not chain height, wallet balance, pool credit or lifetime income. A benchmark's speed is not an earnings estimate. Hardware results depend on driver, epoch, target, thermal conditions and CPU verification load.

12. Find rewards and understand maturity

Use your wallet's Mining Rewards screen and verified synchronization to check rewards belonging to your configured destination. The miner's local acceptance counter is not a substitute for the wallet's chain state.

Solo block rewards have a 1,080-block maturity wait before they become spendable. They mature automatically under the consensus rule; there is no manual claim transaction that bypasses this wait. A visible immature reward cannot yet fund a payment.

The wait is counted in blocks rather than a guaranteed number of hours. Network pauses and chain reorganizations can affect progress. Follow verified confirmation and blocks-remaining information when available.

A pool payout is different from a solo block reward. Pool shares, unpaid pool balance and an actual shielded payment to your wallet are separate records. Check the pool's own payout policy rather than assuming every accepted result creates an immediate wallet payment.

Development fixture blocks demonstrate testing behavior. They are not a promise of transferable public-network coins. Check the network and release status before interpreting a reward display.

13. Multiple GPUs, HiveOS and long sessions

Begin with one successfully tested GPU. In the documented native revision, one miner process selects one device index. There is no multi-device comma-list flag or worker-name option. A second process needs a supported service connection and enough system resources.

Separate device indices do not guarantee distinct nonce ranges. Concurrent processes can duplicate work. Confirm that the node or coordinator supports the intended number of connections and the accounting policy before expanding a rig.

There is no maintained native Onuros HiveOS Flight Sheet adapter established by the current documentation. Do not use another coin's wrapper and assume wallet, pool and statistics fields map correctly. Manual operation on a compatible rig is separate from a tested Flight Sheet integration.

For unattended sessions, first verify stable foreground operation. A service or startup task can supervise the miner, but it cannot fix incorrect credentials, activate a network or provide a missing GPU engine. Retain logs without publishing secrets, and check your rig regularly.

14. Troubleshooting from the first launch

Lowering batch size cannot shrink the epoch DAG. Increasing it cannot remove CPU verification, alter network difficulty or guarantee better utilization. Do not hide a failed self-test with repeated restarts or aggressive overclocking.

15. Protect your PC and your earnings

Use hardware you own or are authorized to operate. Electricity, hardware wear and cooling are real costs. Measure your own power use and do not rely on guaranteed-income claims or another coin's published hashrates.

Keep wallet recovery material separate from mining credentials. A mining token authorizes service access; it is not a wallet backup. Never send the node's private TLS key to the miner or publish credentials in screenshots.

Use conservative clocks for the first sustained run. Monitor temperatures and system stability. Follow hardware manufacturer limits and stop on repeated errors. A briefly successful test does not prove a rig will operate reliably unattended.

Before updating the miner, stop it, record the version and keep your trusted connection files protected. Read compatibility notes and rerun local diagnostics after changes. Do not expose an authenticated service as an unrestricted public listener.

16. Get help without exposing secrets

If you cannot complete a step, contact help@onuros.com or the official Onuros Telegram. Describe your operating system, GPU model, driver version, miner version and the exact nonsecret error. Say whether you are testing locally, using a node or connecting through a pool.

Share only the relevant diagnostic output. Remove authentication tokens, private keys, personal file paths and sensitive connection details. Support does not need your 24 words or wallet password.

If the package differs from the interface described here, use its release-specific instructions. Do not invent settings or install an unofficial replacement offered in a direct message.

Before you start a long session

• The GPU driver works and the correct CUDA engine is present.
• The selected GPU passes its self-test.
• The mining service is compatible and available.
• Your reward destination is confirmed on the same network.
• Native output shows actual accepted work.
• You know how to stop the miner and check verified rewards in your wallet.