Skip to content
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

Open
CaptainMeatloaf opened this issue Dec 11, 2017 · 9 comments
Open

Block unlocker marking all blocks as orphaned #48

CaptainMeatloaf opened this issue Dec 11, 2017 · 9 comments

Comments

@CaptainMeatloaf
Copy link

CaptainMeatloaf commented Dec 11, 2017

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.

image
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 from
apiInterfaces.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.

@CaptainMeatloaf CaptainMeatloaf changed the title Forknote pool not reading block worth correctly Block unlocker marking all blocks as orphaned Dec 12, 2017
@pipozzz
Copy link

pipozzz commented Dec 26, 2017

How did you do reprocessing of bad labeled blocks?

@CaptainMeatloaf
Copy link
Author

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

@BisWang
Copy link

BisWang commented Feb 11, 2018

I have high rate orphan on my turtlecoin pool, but I use the same forknote-pool on intense coin it have normal orphan rate
This problem cause by turtlecoin or?

@CaptainMeatloaf
Copy link
Author

That's a bug in Turtlecoin that we as the pool ops have a fix for - ask on discord.

@pmitchev pmitchev mentioned this issue Mar 12, 2018
@fairmarketcoin
Copy link

what's the fix for this at the coins level?

@alferz
Copy link

alferz commented Mar 18, 2018

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?

@madradio
Copy link

madradio commented Mar 20, 2018

Could anyone of you post the fix for this issue here?

@CaptainMeatloaf
Copy link
Author

You can look at the commit history of TurtleCoin to find the fix, it was done pretty early on

@mohs27
Copy link

mohs27 commented Dec 8, 2021

UPX1YM7hv26AEuddTb648tcRU3SyYAr8AdjA74bkpdJ64H2nFdDt5eRNVBkez1dy8RFBW9enaEqs39gW8QJgv5ei5- - ### - [x] Dp3qq1P56@madradio @mohs27 SAVE_۲۰۲۱۱۲۰۸_۱۰۳۲۲۵.jpg****

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants