What to do when KAS miner is not hashing?

If your KAS miner isn't hashing, check node connectivity, ensure correct wallet format (k: address), verify configuration, and review logs for errors like "failed to fetch work."

Jul 25, 2025 at 12:56 pm

Understanding the Basics of KAS Miner Operation

When KAS miner is not hashing, the first step is to understand how the mining software functions within the Kadena blockchain ecosystem. KAS refers to the native token of the Kadena network, and mining involves solving cryptographic puzzles using computational power to validate transactions and secure the chain. The official mining software, kda-miner, communicates with Kadena’s public chain nodes to receive work units and submit solutions. If the miner shows zero hash rate or fails to report shares, it indicates a breakdown in this communication or execution flow. Ensuring that the miner executable is the latest version is critical, as outdated builds may not support current network protocols. Check the official GitHub repository or Kadena’s mining documentation to verify compatibility.

Verifying Network and Node Connectivity

A common reason for KAS miner not hashing is poor or incorrect connection to a functional Kadena node. The miner must connect to a node that supports mining work distribution, such as a public mining pool or a self-hosted chainweb-node. Confirm the node URL or pool address used in the miner configuration is correct and active. Use tools like curl or a web browser to test access to the node’s API endpoint, typically located at http://:/v1/status. A successful response should return JSON data indicating the node is running and synced. If the connection fails:

• Ensure the firewall allows outbound traffic on the specified port (usually 31257 for mainnet).
• Confirm the node is not rate-limiting or blocking your IP.
• Try switching to an alternative public pool such as https://pool.kda-pool.io or https://kda.f2pool.com.

Reviewing Miner Configuration Files

Improper configuration is a leading cause of KAS miner inactivity. The miner relies on a properly formatted configuration file (often config.yaml or command-line arguments) to define the target node, wallet address, and worker name. Examine the configuration for the following key elements:

• Node URL: Must point to a valid, accessible mining endpoint.
• Wallet Address: Should be a valid Kadena k: address, not a k2: or coinbase: address.
• Worker ID: Optional but recommended for pool identification.
• Thread Count: Must match available CPU cores without overloading the system.

For example, a correct configuration line might look like:

node: "https://us-central1-kda1.kda-pool.io"
wallet: "k:abc123def456..."
worker: "worker-01"
threads: 8

If using command-line execution, ensure arguments are correctly formatted:

./kda-miner --node https://pool.kda-pool.io --wallet k:youraddress --threads 8

Checking System Resources and Background Processes

Even with correct settings, KAS miner may not hash due to system-level constraints. Mining is CPU-intensive, and insufficient resources can halt operation. Monitor CPU usage via Task Manager (Windows) or htop (Linux) to verify the miner process is consuming expected cycles. If CPU usage remains near zero:

• Confirm the antivirus or security software isn’t quarantining or blocking the miner executable.
• Check if the process is paused or suspended by the OS due to thermal throttling.
• Ensure the system isn’t running out of RAM or swap space, which can freeze processes.

Additionally, verify that only one instance of the miner is running. Multiple instances may conflict over resources or network ports. Use ps aux | grep kda-miner on Linux or check the process list on Windows to identify duplicates. Terminate all instances and restart with the correct configuration.

Validating Wallet and Pool Compatibility

A KAS miner not hashing might stem from an incompatible or invalid wallet address. The Kadena network distinguishes between different address types. Mining rewards can only be sent to v1 accounts (k: addresses), not multi-signature (k2:) or smart contract-managed accounts. If the configured wallet uses an unsupported format, the pool will reject the worker registration, resulting in no hashing activity. To verify:

• Use the Kadena Block Explorer to search your wallet address.
• Confirm transactions can be received at this address.
• If using a wallet like Chainweaver, export the correct public key and ensure it maps to a k: address.

Some pools also require explicit wallet registration or email confirmation. Visit the pool’s dashboard and check if your worker appears as “active” or “pending.” If not, re-enter the wallet details on the pool’s website and restart the miner.

Troubleshooting Logs and Error Messages

The miner’s log output is essential for diagnosing why hashing isn’t occurring. Run the miner in a terminal or command prompt to observe real-time logs. Look for recurring error messages such as:

• "Failed to fetch work": Indicates node connectivity issues.
• "Invalid job response": Suggests protocol mismatch or node malfunction.
• "Submit failed: bad-request": Often due to malformed wallet address.
• "No GPU detected": Relevant only if GPU mining is intended (currently, Kadena mining is CPU-only).

Enable verbose logging if available using flags like --verbose or -v. Redirect output to a file for deeper analysis:

./kda-miner --config config.yaml --verbose 2>&1 | tee miner.log

Inspect the log for timestamps and repeated errors. Cross-reference error codes with the Kadena mining FAQ or community forums. Some pools provide status dashboards showing per-worker hash rates—use these to confirm whether the issue is local or network-wide.

Frequently Asked Questions

Q: Can I use a Ledger or Trezor wallet for KAS mining rewards?

No. Hardware wallets generate k2: addresses, which are not compatible with direct mining payouts. Mining pools require k: addresses that can receive native coinbase transactions. To receive rewards, use a software wallet like Chainweaver to generate a v1 account and input that address into the miner.

Q: Why does my miner show "Connected" but still not hash?

This typically means the miner established a TCP connection to the pool but failed to receive a valid work unit. Causes include an incorrect wallet format, temporary node sync lag, or the pool rate-limiting new connections. Wait 2–3 minutes after startup, as initial handshakes may take time. If no hashing begins, restart the miner with verbose logging enabled.

Q: Is it necessary to open specific ports on my router for KAS mining?

No. KAS mining operates as a client connecting outbound to a pool server. Your machine does not need to accept incoming connections. Ensure outbound traffic on port 31257 (or HTTPS 443 for web-based pools) is not blocked by firewall or ISP policies.

Q: How can I test if my node is suitable for solo mining?

To use a self-hosted node for mining, it must run chainweb-node with mining enabled in the configuration. Set enable-mining: true in chainweb-node-config.yaml and expose the API port. Use the miner with --node http://localhost:31257 to connect locally. Monitor the node logs for "mining job dispatched" messages to confirm functionality.