Configuration is self-describing, just copy *config.example.json* to *config.json* and run stratum with path to config file as 1st argument.
```javascript
{
// Address for block rewards
"address": "YOUR-ADDRESS-NOT-EXCHANGE",
"address": "YOUR-ADDRESS-NOT-EXCHANGE", //Please use 'kevacoin-cli getnewaddress' to get the address
// Don't validate address
"bypassAddressValidation": true,
// Don't validate shares
@ -182,8 +196,8 @@ Configuration is self-describing, just copy *config.example.json* to *config.jso
@@ -182,8 +196,8 @@ Configuration is self-describing, just copy *config.example.json* to *config.jso
"host": "127.0.0.1",
"port": 18081,
"timeout": "10s",
"user": "yourusername",
"password": "yourpassword"
"user": "yourusername", //The value should be the same as defined in kevacoin.config
"password": "yourpassword" //The value should be the same as defined in kevacoin.config
}
]
}
@ -191,7 +205,6 @@ Configuration is self-describing, just copy *config.example.json* to *config.jso
@@ -191,7 +205,6 @@ Configuration is self-describing, just copy *config.example.json* to *config.jso
The `upstream` is used to point to the Kevacoin daemon `kevacoind`. The `user` and `password` under `upstream` are mandatory, and they must be the same as the ones specified in Kevacoin configuration file `kevacoin.conf`. You must use `anything.WorkerID` as username in your miner. Either disable address validation or use `<address>.WorkerID` as username. If there is no workerID specified your rig stats will be merged under `0` worker. If mining software contains dev fee rounds its stats will usually appear under `0` worker. This stratum acts like your own pool, the only exception is that you will get rewarded only after block found, shares only used for stats.