... | ... | @@ -85,9 +85,9 @@ Be sure to **wait and sync before mining**. It doesn't take long. |
|
|
|
|
|
To reduce orphan blocks, also be sure to **have peers** and check a block explorer to see the current block number and hash.
|
|
|
|
|
|
Do not key any keys inside the "nokeys" directory.
|
|
|
Do not key any keys inside the "nokeys" directory. You can safely delete `aquaminingdata` and `nokeys` (make sure you dont keep keys in there!)
|
|
|
|
|
|
Run your RPC server like so: `aquachain -rpc -rpcaddr 192.168.1.5 -datadir mining -keystore nokeys -aquabase 0x3317e8405e75551ec7eeeb3508650e7b349665ff`
|
|
|
**Run your RPC server like so: `aquachain -rpc -rpcaddr 192.168.1.5 -datadir aquaminingdata -keystore nokeys -aquabase 0x3317e8405e75551ec7eeeb3508650e7b349665ff`**
|
|
|
|
|
|
Later, to spend and use the AQUA console, just double click aquachain. This way, you keep your keys safe (in the default keystore dir) and don't mix `datadir`, this can prevent RPC attacks.
|
|
|
|
... | ... | @@ -97,9 +97,7 @@ Please see the many cases where people have lost their ETH because leaving RPC o |
|
|
|
|
|
This assumes your AQUA node will be running from LAN 192.168.1.3, with other workers on the same lan.
|
|
|
|
|
|
NODE: `aquachain.exe -keystore nokeys -rpc -rpcaddr 192.168.1.3 -aquabase 0x3317e8405e75551ec7eeeb3508650e7b349665ff`
|
|
|
|
|
|
WORKERS: `aquacppminer --solo -F http://xxx.xxx.xxx.xxx:8543/`
|
|
|
WORKERS: `aquacppminer --solo -F http://192.168.1.3:8543/`
|
|
|
|
|
|
Also consider running a pool! [open-aquachain-pool](https://github.com/aquachain/open-aquachain-pool)
|
|
|
|
... | ... | |