| range (datetime) | range (height)
legendary
Activity: 1092
Merit: 1000
If so, this was implemented in the last fork, i am 100% positive this was not the case before the fork. Fucking developer retard.
This has been in since at least the codebase of 2014/05/28, the first time I grabbed the code. (github history should show any changes there as well anyway) You acting stupid too ? There were no PoS blocks before the last fork, it was broken.
hero member
Activity: 686
Merit: 500
FUN > ROI
If so, this was implemented in the last fork, i am 100% positive this was not the case before the fork. Fucking developer retard.
This has been in since at least the codebase of 2014/05/28, the first time I grabbed the code. (github history should show any changes there as well anyway)
legendary
Activity: 1092
Merit: 1000
Where did you get that number, out of your ass ? "Actually", looking at your pool stats (possibly bug-driven) or devs posting history?
It's in the code. main.h
STAKE_TARGET_SPACING = 90; // 90 second block spacing
main.cpp
static const int64 nTargetSpacingWorkMax = 10 * STAKE_TARGET_SPACING; // 15 minutes
Then there's a whole section that deals with the interval some more. If so, this was implemented in the last fork, i am 100% positive this was not the case before the fork. Fucking developer retard.
hero member
Activity: 686
Merit: 500
FUN > ROI
Where did you get that number, out of your ass ? "Actually", looking at your pool stats (possibly bug-driven) or devs posting history?
It's in the code. main.h
STAKE_TARGET_SPACING = 90; // 90 second block spacing
main.cpp
static const int64 nTargetSpacingWorkMax = 10 * STAKE_TARGET_SPACING; // 15 minutes
Then there's a whole section that deals with the interval some more.
legendary
Activity: 1092
Merit: 1000
Max target for PoW is actually 15 min. Where did you get that number, out of your ass ? "Actually", looking at your pool stats (possibly bug-driven) or devs posting history?
hero member
Activity: 616
Merit: 500
Max target for PoW is actually 15 min.
legendary
Activity: 1092
Merit: 1000
hero member
Activity: 616
Merit: 500
"networkghps" : 0.00205548, How much is this in MH/s ?
Last I checked, there were a thousand megas in a giga. So approximately 2Mhash/s. You'll want to get multiple readings over, say, an hour or so, given the constant difficulty adjustment, the estimate bounces around as well. Only 2Mhash/s ?? The pool alone is doing 1Mhash/s so should be getting 50% of all PoW blocks ? Instead its hitting one block every couple of hours ?? How is this possible ? slimcoin 2014-6-24 15:02:22 UTC 19485 000000044b6cd55ad887d022d0e3d2efdd9039d14d63408a8dcb5e14ec045bc3 9.36 immature slimcoin 2014-6-24 13:29:25 UTC 19431 00000000f7c59c2bc135a41bc7b5d7c48840acdfd354a3e52e2b8b90a716f8db 8.64 immature last two blocks pool found - 1hour 30min difference This time you are right primer  Sandor take a close look at your logfiles... That is definitely worse than "bad luck". Take some action, fast please! My first guess would be you're on a version of the node.js stratum that has the "block invalid" bug.. meaning a found block is is rejected in the stratum, but accepted in the client. Stratum and DB however do not notice that and the block is not counted at all There is nothing wrong with the pool... there are actually no blocks being rejected, all 100% submitted. Btw there were only 4 PoW blocks generated between 19431 and 19485 : 19467, 19477, 19479, 19480 It's basic statistics, primer-. If the network hashrate was 2 Mh/s, that means we would get 50% over the long run. BUT, since the sample size is only 4 blocks that means that the spread is large, so nothing alarming that the pool mined two less blocks than it was supposed to. Compare it to flipping a coin 4 times and getting 4x tail in a row. There were only 4 PoW blocks (which should spawn every 90 secs) in 1.5 hours ?? And dont patronize me with basic statistics, instead of wasting characters about statistics you should have wrote something about a broken algo - PoW block should be created every 90 secs not one every 30 minutes! Where does it say that PoW blocks are created every 90 seconds?
legendary
Activity: 1092
Merit: 1000
"networkghps" : 0.00205548, How much is this in MH/s ?
Last I checked, there were a thousand megas in a giga. So approximately 2Mhash/s. You'll want to get multiple readings over, say, an hour or so, given the constant difficulty adjustment, the estimate bounces around as well. Only 2Mhash/s ?? The pool alone is doing 1Mhash/s so should be getting 50% of all PoW blocks ? Instead its hitting one block every couple of hours ?? How is this possible ? slimcoin 2014-6-24 15:02:22 UTC 19485 000000044b6cd55ad887d022d0e3d2efdd9039d14d63408a8dcb5e14ec045bc3 9.36 immature slimcoin 2014-6-24 13:29:25 UTC 19431 00000000f7c59c2bc135a41bc7b5d7c48840acdfd354a3e52e2b8b90a716f8db 8.64 immature last two blocks pool found - 1hour 30min difference This time you are right primer Sandor take a close look at your logfiles... That is definitely worse than "bad luck". Take some action, fast please! My first guess would be you're on a version of the node.js stratum that has the "block invalid" bug.. meaning a found block is is rejected in the stratum, but accepted in the client. Stratum and DB however do not notice that and the block is not counted at all There is nothing wrong with the pool... there are actually no blocks being rejected, all 100% submitted. Btw there were only 4 PoW blocks generated between 19431 and 19485 : 19467, 19477, 19479, 19480 It's basic statistics, primer-. If the network hashrate was 2 Mh/s, that means we would get 50% over the long run. BUT, since the sample size is only 4 blocks that means that the spread is large, so nothing alarming that the pool mined two less blocks than it was supposed to. Compare it to flipping a coin 4 times and getting 4x tail in a row. There were only 4 PoW blocks (which should spawn every 90 secs) in 1.5 hours ?? D Dont patronize me with basic statistics, instead of wasting characters about statistics you should have wrote something about a broken algo - PoW block should be created every 90 secs not one every 30 minutes! EDIT : I did check 20-30 blocks from 19431 and they all seems to be PoS or PoB.. Algo is obviously broken, PoW blocks are not created as stated in the whitepaper, one every 90 sec. What is causing this, PoS and PoB blocks ?
hero member
Activity: 616
Merit: 500
"networkghps" : 0.00205548, How much is this in MH/s ?
Last I checked, there were a thousand megas in a giga. So approximately 2Mhash/s. You'll want to get multiple readings over, say, an hour or so, given the constant difficulty adjustment, the estimate bounces around as well. Only 2Mhash/s ?? The pool alone is doing 1Mhash/s so should be getting 50% of all PoW blocks ? Instead its hitting one block every couple of hours ?? How is this possible ? slimcoin 2014-6-24 15:02:22 UTC 19485 000000044b6cd55ad887d022d0e3d2efdd9039d14d63408a8dcb5e14ec045bc3 9.36 immature slimcoin 2014-6-24 13:29:25 UTC 19431 00000000f7c59c2bc135a41bc7b5d7c48840acdfd354a3e52e2b8b90a716f8db 8.64 immature last two blocks pool found - 1hour 30min difference This time you are right primer Sandor take a close look at your logfiles... That is definitely worse than "bad luck". Take some action, fast please! My first guess would be you're on a version of the node.js stratum that has the "block invalid" bug.. meaning a found block is is rejected in the stratum, but accepted in the client. Stratum and DB however do not notice that and the block is not counted at all There is nothing wrong with the pool... there are actually no blocks being rejected, all 100% submitted. Btw there were only 4 PoW blocks generated between 19431 and 19485 : 19467, 19477, 19479, 19480 It's basic statistics, primer-. If the network hashrate was 2 Mh/s, that means we would get 50% over the long run. BUT, since the sample size is only 4 blocks that means that the spread is large, so nothing alarming that the pool mined two less blocks than it was supposed to. Compare it to flipping a coin 4 times and getting 4x tail in a row.
full member
Activity: 126
Merit: 100
You run several wallet with the same wallet.dat ?
Yes Ok, I am sync 2 more wallet, will see.
|
BROKEN, dev better fix it in the next update. 