-
**Environment**
Devices: All asicboost compatible SHA256 miners
**Steps to Reproduce**
1. Have ASICseer ops connect compatible units to test pool
2. Verify correct starting and automatic difficu…
-
Please help me to understand diff and var diff settings!
I got a miner, who claims to need high difficulty settings. My settings are yet:
```
"ports": {
"4445": {
"diff": 1024,
"…
-
Can we have a new vardiff order so we don't have random share diffs but could set intervals from the base share diff, such as
VDIFF_BASE_TARGET = 16 # Base Share Difficulty
VDIFF_INTERVALS = 4 # Numb…
-
I've been running on an old version (circa 2 yr old) for awhile. Recently tried starting up a new copy, ran into this issue with a barely modified example config:
powerpool.exceptions.Configuratio…
-
Hi,
Thanks for this proxy! I'm trying to use it with Hashvault which says I can set the username to `wallet+DIFF` to fix the difficulty of the shares (which I don't think it works, it seems to be v…
aleqx updated
6 years ago
-
Vardiff seems to adjust in multiples - 8,16,32,64,128 and so on. Is there a way this can be brought down to as low as single step increments or even decimals so miner hashrate can be more accurately …
-
I'm running a pool with https://github.com/moopless/stratum-mining-litecoin 's master branch and lately I've set vardiff=true to test it out.
my current vardiff setup is;
```
# ******************** …
-
I set up a pool following the guide,but get an error as follows:
[2018-03-15T07:40:26.126Z] [warn] [raven] [PaymentProcessor] : Could not decrypt address from tx (no tx.result or tx.address field) {"…
-
After speaking with @obigal, I am now aware of an issue with the vardiff algorithm where it does not work for coins that have a difficulty below 1. I have proposed two solutions.
1. Multiply the diffi…
-
Although I think we should probably not actually rigidly follow the difficulty specified, or a malicious user could flood the server with low difficulty shares, we should probably never adjust to a di…