How to mine Scash with a CPU

Setup sequence

Choose the right software and platform

The node and miner are separate programs. Solo mining needs both; a pool can supply work to a miner without a local node. The cpuminer-scash 3.0.9 release provides the following packages, checked on 22 September 2026:

Match your operating system and CPU architecture, download SHA256SUMS from the same release, and compare the archive’s SHA-256 digest before extracting it. On Linux use sha256sum FILE.tgz; on macOS use shasum -a 256 FILE.tgz; on Windows PowerShell use Get-FileHash .\FILE.tgz -Algorithm SHA256. Replace the example filename with the downloaded archive. A checksum checks consistency with the publisher’s file, not whether the software is safe.

From download to first hash

1. Download and verify the software.

   Get the Scash node and cpuminer-scash from their project release pages. Review release notes and checksums where provided; do not install binaries received through direct messages.

2. Create a receiving address.

   Create or load a wallet, encrypt it, make a tested offline backup, and generate an address for mining rewards. Never put private keys, wallet files, or passwords in a miner command.

3. Configure solo or pool mining.

   For solo mining, enable authenticated RPC on a synchronized node and point the miner at it. For a pool, use the exact server, port, username format, and TLS guidance published by that pool.

4. Start conservatively.

   Begin with fewer threads, monitor temperature and power draw, then adjust thread count and large-page settings for your hardware and operating system.

5. Monitor accepted work.

   Confirm that the miner reports accepted shares or valid node work. Investigate repeated connection failures, rejected shares, overheating, or unexpected hashrate changes.

Example solo-mining command

After configuring authenticated RPC and replacing every placeholder, a local setup follows this general form:

./minerd -o 127.0.0.1:8342 \
  -O RPC_USERNAME:RPC_PASSWORD \
  -t 4 \
  --coinbase-addr=YOUR_SCASH_ADDRESS

The current miner help output and repository instructions are authoritative if an option changes. Do not expose the node RPC port to the public internet.

This syntax follows the miner’s published usage instructions. RPC credentials in command arguments can appear in process listings or shell history; use a dedicated local account and consult the miner’s configuration options when sharing a machine.

Troubleshoot the first connection

Connection refused

Check that the node is running with RPC enabled, that the miner points to the same machine, and that the port is correct. The documented mainnet RPC port is 8342; the peer-to-peer port is 8343. Do not solve a local connection problem by exposing RPC publicly.

Authentication failed

Use the node’s RPC credentials for solo mining. Pool logins use the pool’s own wallet/worker format and are not interchangeable with node credentials.

No work or repeated rejected shares

Check node synchronization for solo mining, or the pool’s current endpoint, TLS requirements, worker format, and supported software versions. Read the actual error before changing performance settings.

Large pages fail or the system slows down

First test without optional large-page settings and with fewer threads. Check free memory and temperature, then follow the operating-system-specific guidance in the miner repository.

Mining runs but no reward arrives

Hashing does not guarantee finding a solo block. For pool mining, check accepted shares, the payout address, minimum payout, and the pool’s reward rules.

Source: protocol network ports. For software maintenance and node packages, read the wallet setup guide.