Re: [ANN] Diamond (DMD) Evolution v 2.0 | NEW wallet, coin mechanics, 50% POS
Hi Danbi!
Thanks so much for this info. I added this parameter and now pool is accepting blocks. However with almost 20 hours of 20mhs I could not find any blocks yet.
Do I need to do anything else? Perhaps disable POS in the wallet?
The miner is correct, it gets accepted shares on your pool and I have latest NOMP from github.
Thanks in advance!
srcxxx
Oh, I forgot this bit of the instructions. Must have (as usual) assumed it was obvious.
Thing is, GroestlCoin is actually deviating from the common standard, in that it (and few other new coins) is not using sha256d for the transaction hashes, but sha256 (single pass). To accomodate GroestlCoin, NOMP and sph-sgminer actually threat it as special case. In summary, it was never the new DMD wallet's fault that stratum mining did not work -- it was how that software assumed that when you said you want "groestl" you also said you want sha256 (single).
NOMP already has a setting to fix this, thanks to some discussion with the author. For coins that use any of (currently) keccak, blake, fugue and groestl -- you need to specify
in the coin definition.
By the way, the morale of this story is that the DMD team has been blamed without guilt on this subject.
Thanks so much for this info. I added this parameter and now pool is accepting blocks. However with almost 20 hours of 20mhs I could not find any blocks yet.
Do I need to do anything else? Perhaps disable POS in the wallet?
The miner is correct, it gets accepted shares on your pool and I have latest NOMP from github.
Thanks in advance!
srcxxx
Hi pool operators using NOMP!
What is your diamond.json? Something like this?
Thanks!
What is your diamond.json? Something like this?
Code:
{
"name": "Diamondcoin",
"symbol": "DMD",
"algorithm": "groestl",
"txMessages": true
}
"name": "Diamondcoin",
"symbol": "DMD",
"algorithm": "groestl",
"txMessages": true
}
Thanks!
Oh, I forgot this bit of the instructions. Must have (as usual) assumed it was obvious.
Thing is, GroestlCoin is actually deviating from the common standard, in that it (and few other new coins) is not using sha256d for the transaction hashes, but sha256 (single pass). To accomodate GroestlCoin, NOMP and sph-sgminer actually threat it as special case. In summary, it was never the new DMD wallet's fault that stratum mining did not work -- it was how that software assumed that when you said you want "groestl" you also said you want sha256 (single).
NOMP already has a setting to fix this, thanks to some discussion with the author. For coins that use any of (currently) keccak, blake, fugue and groestl -- you need to specify
Code:
"normalHashing": true,
in the coin definition.
By the way, the morale of this story is that the DMD team has been blamed without guilt on this subject.