Skip to main content
Solo mining sends your hashrate to your own Parallax node instead of a pool. Each block you find pays the whole block reward to you, but blocks come irregularly: a small rig can go a long time without one. On a pool, rewards come in small, regular amounts instead; see Pool Mining.

​
Step-by-step Guide

1

Start your node with mining enabled

Run the Parallax client with the mining API and the address that receives the rewards:
The node must be synced: until then it has no work to give.
2

Point Hashwarp to it

The block reward goes to the node’s --miner.coinbase address: Hashwarp doesn’t need --wallet for solo mining.
3

Wait for a block

Each block found is logged with its height:
The reward can be spent once the block has 100 blocks on top of it. Check your balance with:
Keep the node’s HTTP and WebSocket ports on your local network: the mining API has no authentication, so anyone who can reach it can submit work to your node.

​
New work without polling: WebSocket

Over HTTP, Hashwarp asks the node for new work every second (--getwork-interval, in milliseconds). Over the node’s WebSocket, the node can instead push each new block’s work to Hashwarp the moment it has it, and blocks go back on the same connection:
When the node pushes work, Hashwarp says so when it connects:
Pushing new work needs a Parallax client that supports the newWork subscription. With an older client, Hashwarp asks for work on the same WebSocket every --getwork-interval milliseconds instead, and says so when it connects: mining works the same.
wss:// works with a node behind a TLS proxy.

​
Solo with a failover pool

Solo mining combines with failover pools: Hashwarp mines on the pool while the node is unreachable, and moves back to the node with --failover-timeout:

​
Options