zone117x
groestl myriad
I have manage to tweak the code in order to find valid share and valid block. Unfortunaletly NOMP is unable to detect them. It tells me :
We thought a block was found but it was rejected by the daemon,
But I can see that the block is a valid one in my wallet. Do you know where I have to look in order to fix this issue ? I had the same with the skein algo.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
Is the block indeed accepted by the daemon? If so then it means that NOMP isn't generating the correct block hash for checking. What did you have to tweak to get valid shares & blocks accepted for that coin? The coinbase tx hashing algo?
We'd like to add two optional configs to the coin.json definitions to specify the hashing algo used for coinbase tx and block hash so these odd coins can be supported.
The block was accepted by the daemon indeed. Finally I realized that what I did produce the same result that what was already there (there is a groestl_myriad hashing function that already exist in your code).
So I don't know what need to be change in order to fix it.
The problem is that Myriad has 2 hashes - the POW hash and the real block hash. The stratum submits the POW hash to the coin daemon via RPC, then checks that the block was accepted by issuing a getblock rpc command using the same hash. This will not be found because the stratum is using the POW hash which is a Groestl hash, whereas the block hash is hashed using SHA256D.
The way I fixed this (on another multi-algo coin) was to modify jobManager.cs line 232: Replace: blockHash = blockHasher(headerBuffer, nTime).toString('hex'); With: blockHash = util.reverseBuffer(util.sha256d(headerBuffer, nTime)).toString('hex');
I could probably submit a pull request to fix this soon by introducing a new coin option 'multiAlgo'
Thank you Griffitsj for your recomendation. It does work.
If anyone needs it, see two commits here:
https://github.com/srcxxx/node-stratum-pool/commit/e6c983299ce45af464fe81d5ccdde2992ebab5e3
https://github.com/srcxxx/node-stratum-pool/commit/1039fc3c5912e5a6871907ce2aa424eff481959c
I am getting similar errors when running a Digibyte-skein pool. The pool finds valid blocks, but nomp thinks they are not valid, payment processing seems to not work correctly.
We thought a block was found but it was rejected by the daemon, share data:
Has this issue been formally resolved?
@jabiers block hash is different with submitted hash the block hash of DGB is sha256d
