-
Notifications
You must be signed in to change notification settings - Fork 182
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Block unlocker marking all blocks as orphaned #48
Comments
How did you do reprocessing of bad labeled blocks? |
I didn't - as I was solo mining and it was a testing phase for the pool, all the blocks found went to me anyway |
I have high rate orphan on my turtlecoin pool, but I use the same forknote-pool on intense coin it have normal orphan rate |
That's a bug in Turtlecoin that we as the pool ops have a fix for - ask on discord. |
what's the fix for this at the coins level? |
Same issue on leviarcoin. I made the same fix as OP, but does anyone have a better one? Maybe an option in the config file to address the off by one issue for crappily coded coins? |
Could anyone of you post the fix for this issue here? |
You can look at the commit history of TurtleCoin to find the fix, it was done pretty early on |
…o fix orphaned block issue with some coins, see: forknote/forknote-pool#48
UPX1YM7hv26AEuddTb648tcRU3SyYAr8AdjA74bkpdJ64H2nFdDt5eRNVBkez1dy8RFBW9enaEqs39gW8QJgv5ei5- - ### - [x] Dp3qq1P56@madradio @mohs27 **** |
I'm attempting to set up a pool for turtlecoin (https://github.com/turtlecoin/turtlecoin), at http://turtlepool.space, and appear to be having issues with getting the pool to unlock the blocks correctly.
UPDATE: For those using TurtleCoin, this was fixed, this bug still may apply to other cryptonote currencies.
I have set up the daemon and wallet (using simplewallet), and the pool appears to connect to them and read ok.
I then set up my miner to mine to the pool. It has managed to find several successful blocks, however when a block is discovered, the block becomes orphaned after the maturity depth has passed.
There are no obvious errors in any of the logs.
Upon further inspection, it appears that there is an off-by-one error in blockUnlocker.js.
This can be temporarily fixed by changing line 48 of
blockUnlocker.js
fromapiInterfaces.rpcDaemon('getblockheaderbyheight', {height: block.height}, function(error, result){
to
apiInterfaces.rpcDaemon('getblockheaderbyheight', {height: block.height + 1}, function(error, result){
However this feels like somewhat of a hack.
Please let me know if you need any more info.
The text was updated successfully, but these errors were encountered: