silklich
Full Member
Offline
Activity: 394
Merit: 100
i like Phore
|
|
September 21, 2017, 02:26:57 PM |
|
my wallet dont connect network.... Is there any working node??
|
|
|
|
Yukin
Member
Offline
Activity: 84
Merit: 10
|
|
September 21, 2017, 02:50:28 PM |
|
my wallet dont connect network.... Is there any working node??
addnode=107.191.55.64:10809 addnode=198.12.70.154:10809 addnode=88.99.173.100:10809 addnode=91.121.82.70:10809 addnode=157.161.128.61:10809 addnode=66.228.57.25:10809 addnode=83.169.7.202:10809 addnode=138.68.108.250:10809 https://www.cryptopia.co.nz/CoinInfo/?coin=SCOREenjoy!
|
|
|
|
LycheeBit
|
|
September 21, 2017, 04:00:56 PM |
|
Hello Here is a new mining pool for mining Scorecoin. It's based on YiiMP, no registration is needed : - Stratum : lycheebit.com:3433
- User : YOUR_SCORE_ADDRESS
- Password : c=SCORE
Exemple of CCMiner command line : ccminer.exe -a scrypt -o stratum+tcp://lycheebit.com:3433 -u SZQZBCDEQnEzsYqzeZD5ZNmB8qDJWfoNg6 -p c=SCORE Happy mining
|
|
|
|
mrhans
|
|
September 21, 2017, 05:57:51 PM |
|
@mark
have you ever considered simply merging both coins? Wouldn't that make more sense then two coins with the exact same features? Easier for a wider adoption
|
|
|
|
suprnurd
Member
Offline
Activity: 250
Merit: 12
Support Guru
|
|
September 21, 2017, 06:12:15 PM |
|
hey Mark how goes development?
|
|
|
|
bobitza202
|
|
September 21, 2017, 06:56:12 PM |
|
What do Scorecoin holders need to do when the hard fork comes? will there be a swap?of just a wallet update?
|
|
|
|
silklich
Full Member
Offline
Activity: 394
Merit: 100
i like Phore
|
|
September 22, 2017, 03:23:24 AM |
|
my wallet dont connect network.... Is there any working node??
addnode=107.191.55.64:10809 addnode=198.12.70.154:10809 addnode=88.99.173.100:10809 addnode=91.121.82.70:10809 addnode=157.161.128.61:10809 addnode=66.228.57.25:10809 addnode=83.169.7.202:10809 addnode=138.68.108.250:10809 https://www.cryptopia.co.nz/CoinInfo/?coin=SCOREenjoy! WoW!!! it's working!! thanks bro!
|
|
|
|
kurbeks
|
|
September 22, 2017, 06:51:58 AM |
|
What do Scorecoin holders need to do when the hard fork comes? will there be a swap?of just a wallet update?
Should be wallet update
|
|
|
|
~Money~
|
|
September 22, 2017, 12:08:23 PM Last edit: September 22, 2017, 12:19:12 PM by ~Money~ |
|
score is one of my favt coin infect i keep buy @ every dip ... if dev can bring score on bittrex then it will be on moon
|
|
|
|
Shankar94
Full Member
Offline
Activity: 140
Merit: 100
DeepOnion ♡
|
|
September 22, 2017, 12:35:08 PM |
|
|
|
|
|
Fadayko
Newbie
Offline
Activity: 21
Merit: 0
|
|
September 22, 2017, 06:39:10 PM |
|
We have an issue on the coincave.nl mining pool where we are discovering blocks that have already been found. This is then forcing the unconfirmed shares of the original block to be orphaned. Please fix this as we have spent time and energy to discover these blocks and now we are working back through the blockchain for the second time. This occured in a series of 54 blocks.
Thank you,
|
|
|
|
Spekske
|
|
September 22, 2017, 06:48:17 PM |
|
We have an issue on the coincave.nl mining pool where we are discovering blocks that have already been found. This is then forcing the unconfirmed shares of the original block to be orphaned. Please fix this as we have spent time and energy to discover these blocks and now we are working back through the blockchain for the second time. This occured in a series of 54 blocks.
Thank you,
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 also find a weird entry in the nodes list that keeps connected all the time, anyone has an idea what this might be ? ip address: 40.71.81.210:34772 protocol version 70004 Satoshi:0.8.88.84
|
|
|
|
Fadayko
Newbie
Offline
Activity: 21
Merit: 0
|
|
September 22, 2017, 06:54:36 PM |
|
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.
|
|
|
|
Spekske
|
|
September 22, 2017, 06:57:17 PM |
|
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.
|
|
|
|
Fadayko
Newbie
Offline
Activity: 21
Merit: 0
|
|
September 22, 2017, 07:03:22 PM |
|
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?
|
|
|
|
Spekske
|
|
September 22, 2017, 07:05:46 PM |
|
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.
|
|
|
|
Fadayko
Newbie
Offline
Activity: 21
Merit: 0
|
|
September 22, 2017, 07:13:06 PM |
|
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
|
|
|
|
Spekske
|
|
September 22, 2017, 07:16:28 PM |
|
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 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.
|
|
|
|
Spekske
|
|
September 22, 2017, 07:21:02 PM |
|
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 Going to try 1 quick change to see if that makes any difference, daemon will be offline for a minute....
|
|
|
|
Fadayko
Newbie
Offline
Activity: 21
Merit: 0
|
|
September 22, 2017, 07:24:49 PM |
|
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 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.
|
|
|
|
|