Quote from: Fadayko on September 22, 2017, 07:24:49 PM

Quote from: Spekske on September 22, 2017, 07:16:28 PM

Quote from: Fadayko on September 22, 2017, 07:13:06 PM

Quote from: Spekske on September 22, 2017, 07:05:46 PM

Quote from: Fadayko on September 22, 2017, 07:03:22 PM

Quote from: Spekske on September 22, 2017, 06:57:17 PM

Quote from: Fadayko on September 22, 2017, 06:54:36 PM

Quote

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/2248

I 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

The configuration is no different than any of the other coins, check TRADE or BAT, they run fine, so for now there is not much I can do from here. I have the impression that there is an alternative blockchain running that crosses the correct one frequently based on those rewrites in the debug.log.

Well...I appreciate your time and talking through the issue. We will see what the Dev has to say at a later time and hopefully reach a resolution.

At this moment there is no movement at all in the blockchain. All seems to point to errors in the network and/or the code. As an extra test I have just setup an extra NOMP based miningpool on my secondary server. If anyone wants to give it a try just to see if we can break this thing free please go ahead! Use the following URL:

http://coincave.nl:8080

Ports available:

stratum+tcp://coincave.nl:3510 vardiff 8-65536 (starts at 32)
stratum+tcp://coincave.nl:3511 diff 8
stratum+tcp://coincave.nl:3512 diff 256
stratum+tcp://coincave.nl:3513 diff 512
stratum+tcp://coincave.nl:3514 diff 1024
stratum+tcp://coincave.nl:3515 diff 2048
stratum+tcp://coincave.nl:3516 diff 4096
stratum+tcp://coincave.nl:3517 diff 8192
stratum+tcp://coincave.nl:3518 diff 16384
stratum+tcp://coincave.nl:3519 diff 32768