According to the blockexplorer and the daemon behind coincave the current height is 132382. I have no idea where those blocks beyond that height are coming from. All I know is that an experimental code has been online for a few days which might be screwing up things if people downloaded it and are using it. I find multiple entries in the debug.log where the blockchain is altered.
I agree. In my transaction log I have already discovered block 132382 and now I am reworking the block. And with coincave requiring 120 confirmations there is no guarantee that even the current block wont be deemed and orphan for the second time.
Those 120 confirmations are a temporary setting as long as there are these kind of issues. Once the code is updated and fully errorfree confirmations will be changed to match those in the coinsource.
So in theory all the orphaned blocks are altered to a confirmed status and I receive the shares for the completed block?
The issue is in the coin source, not the pool, check this link:
https://github.com/MPOS/php-mpos/issues/2248I think the dev should really get cracking and solve these issues that currently only happen with score, most other coins are running without too many issues.
Interesting... I wish they would of closed the subject with a resolution...regardless whether its a coin source issue or an anomaly with the pool configuration the issue is a detriment to mining on coincave.nl...which I prefer over our other pools. From my experience with mining dutch they do not have this as an issue. It seems like coincave has an issue when the difficulty levels are +/- 300