IanFoxley
Legendary
Offline
Activity: 910
Merit: 1000
|
|
January 04, 2014, 09:29:45 PM |
|
When somebody donates at least 0.01 CAT and I see everything works correctly I'll make a thread about my faucet - Catcoin PurrerI sent you 0.1 CAT, hope that was ok. Edited: Oh I can see it shows 0.1 CAT remaining on the websites front page. Guess it did work then.
|
|
|
|
vaelrock
|
|
January 04, 2014, 09:32:45 PM |
|
Nobody ever spoke of a new retarget time, so it cannot be anything else than a bug of the new client. Difficulty changed after 14 blocks instead of 36. 4 for 10mn target time ~= 28MH/s on the network. This is not possible.
I don't know how it's recalculated, but I believe it's always aiming for 10 minutes block time. Maybe it just needed another adjustment before it could get it right for the next change. Diff retarget is supposed to happen after 36 blocks, or at block 20290+36 = 20326. It happened at block 20304, which is 14 blocks. Blocks were found every 5mn, if a retarget should have come sooner, it should have increase to 30, not go down all the way to 4. Pray for it not to go down to 1 in 2 blocks (20318).
|
|
|
|
Nullu
|
|
January 04, 2014, 09:34:07 PM |
|
next diff 1???
Where are you seeing that?
|
BTC - 14kYyhhWZwSJFHAjNTtyhRVSu157nE92gF
|
|
|
rizardus
Member
Offline
Activity: 112
Merit: 10
|
|
January 04, 2014, 09:35:35 PM |
|
somethings is wrong, pools didnt find block
|
|
|
|
Nullu
|
|
January 04, 2014, 09:36:03 PM |
|
Nobody ever spoke of a new retarget time, so it cannot be anything else than a bug of the new client. Difficulty changed after 14 blocks instead of 36. 4 for 10mn target time ~= 28MH/s on the network. This is not possible.
I don't know how it's recalculated, but I believe it's always aiming for 10 minutes block time. Maybe it just needed another adjustment before it could get it right for the next change. Diff retarget is supposed to happen after 36 blocks, or at block 20290+36 = 20326. It happened at block 20304, which is 14 blocks. Blocks were found every 5mn, if a retarget should have come sooner, it should have increase to 30, not go down all the way to 4. Pray for it not to go down to 1 in 2 blocks (20318). Conium is on 20322
|
BTC - 14kYyhhWZwSJFHAjNTtyhRVSu157nE92gF
|
|
|
TBCM
|
|
January 04, 2014, 09:36:37 PM |
|
When somebody donates at least 0.01 CAT and I see everything works correctly I'll make a thread about my faucet - Catcoin PurrerI sent you 0.1 CAT, hope that was ok. Edited: Oh I can see it shows 0.1 CAT remaining on the websites front page. Guess it did work then. Thanks, that will be enough to give a taste of the coin to some new people. Thread created.
|
|
|
|
|
Nullu
|
|
January 04, 2014, 09:37:04 PM |
|
Has one of the pools forked the fork?
|
BTC - 14kYyhhWZwSJFHAjNTtyhRVSu157nE92gF
|
|
|
envy2010
|
|
January 04, 2014, 09:37:18 PM |
|
Nobody ever spoke of a new retarget time, so it cannot be anything else than a bug of the new client. Difficulty changed after 14 blocks instead of 36. 4 for 10mn target time ~= 28MH/s on the network. This is not possible.
I don't know how it's recalculated, but I believe it's always aiming for 10 minutes block time. Maybe it just needed another adjustment before it could get it right for the next change. Diff retarget is supposed to happen after 36 blocks, or at block 20290+36 = 20326. It happened at block 20304, which is 14 blocks. Blocks were found every 5mn, if a retarget should have come sooner, it should have increase to 30, not go down all the way to 4. Pray for it not to go down to 1 in 2 blocks (20318). It happened at the next multiple of 36. That is, 564*36 blocks = 20304. It went down to 4 because it used the time from block 20268 to block 20304 as the basis for the diff calculation, and that was several days instead of the target 6 hours. The next one will go up.
|
|
|
|
vaelrock
|
|
January 04, 2014, 09:38:04 PM |
|
Nobody ever spoke of a new retarget time, so it cannot be anything else than a bug of the new client. Difficulty changed after 14 blocks instead of 36. 4 for 10mn target time ~= 28MH/s on the network. This is not possible.
I don't know how it's recalculated, but I believe it's always aiming for 10 minutes block time. Maybe it just needed another adjustment before it could get it right for the next change. Diff retarget is supposed to happen after 36 blocks, or at block 20290+36 = 20326. It happened at block 20304, which is 14 blocks. Blocks were found every 5mn, if a retarget should have come sooner, it should have increase to 30, not go down all the way to 4. Pray for it not to go down to 1 in 2 blocks (20318). Conium is on 20322 Ok so multiple pool must be on a different block chain. There's the explanation of the diff to 4 ...
|
|
|
|
Nullu
|
|
January 04, 2014, 09:38:26 PM |
|
Nobody ever spoke of a new retarget time, so it cannot be anything else than a bug of the new client. Difficulty changed after 14 blocks instead of 36. 4 for 10mn target time ~= 28MH/s on the network. This is not possible.
I don't know how it's recalculated, but I believe it's always aiming for 10 minutes block time. Maybe it just needed another adjustment before it could get it right for the next change. Diff retarget is supposed to happen after 36 blocks, or at block 20290+36 = 20326. It happened at block 20304, which is 14 blocks. Blocks were found every 5mn, if a retarget should have come sooner, it should have increase to 30, not go down all the way to 4. Pray for it not to go down to 1 in 2 blocks (20318). It happened at the next multiple of 36. That is, 564*36 blocks = 20304. It went down to 4 because it used the time from block 20268 to block 20304 as the basis for the diff calculation, and that was several days instead of the target 6 hours. The next one will go up. I'm glad someone here knows there stuff. Phew. Was almost in a panic then.
|
BTC - 14kYyhhWZwSJFHAjNTtyhRVSu157nE92gF
|
|
|
Nullu
|
|
January 04, 2014, 09:40:06 PM |
|
Nobody ever spoke of a new retarget time, so it cannot be anything else than a bug of the new client. Difficulty changed after 14 blocks instead of 36. 4 for 10mn target time ~= 28MH/s on the network. This is not possible.
I don't know how it's recalculated, but I believe it's always aiming for 10 minutes block time. Maybe it just needed another adjustment before it could get it right for the next change. Diff retarget is supposed to happen after 36 blocks, or at block 20290+36 = 20326. It happened at block 20304, which is 14 blocks. Blocks were found every 5mn, if a retarget should have come sooner, it should have increase to 30, not go down all the way to 4. Pray for it not to go down to 1 in 2 blocks (20318). Conium is on 20322 Ok so multiple pool must be on a different block chain. There's the explanation of the diff to 4 ... No, 4 is right, but we're on block 20322. I think the pool forgot to update the diff calculation or something, conium still shows; Difficulty 4 Est Next Difficulty 26.40859256 (Change in 1854 Blocks It's not updated the change on the front end.
|
BTC - 14kYyhhWZwSJFHAjNTtyhRVSu157nE92gF
|
|
|
vaelrock
|
|
January 04, 2014, 09:40:29 PM |
|
It doesn't explain why coinium is at a block greater than the official blockchain. They must have forgot to update.
|
|
|
|
Nullu
|
|
January 04, 2014, 09:42:48 PM |
|
doesn't explain why coinium is at a block greater than the official blockchain.
Doesn't the blockchain show the last mined block, and the pool show the block it's currently mining?
|
BTC - 14kYyhhWZwSJFHAjNTtyhRVSu157nE92gF
|
|
|
CatCoinForums
Member
Offline
Activity: 98
Merit: 10
|
|
January 04, 2014, 09:43:37 PM |
|
no you're not lol, poolerino is :facepalm:
|
|
|
|
vaelrock
|
|
January 04, 2014, 09:43:46 PM |
|
Nobody ever spoke of a new retarget time, so it cannot be anything else than a bug of the new client. Difficulty changed after 14 blocks instead of 36. 4 for 10mn target time ~= 28MH/s on the network. This is not possible.
I don't know how it's recalculated, but I believe it's always aiming for 10 minutes block time. Maybe it just needed another adjustment before it could get it right for the next change. Diff retarget is supposed to happen after 36 blocks, or at block 20290+36 = 20326. It happened at block 20304, which is 14 blocks. Blocks were found every 5mn, if a retarget should have come sooner, it should have increase to 30, not go down all the way to 4. Pray for it not to go down to 1 in 2 blocks (20318). It happened at the next multiple of 36. That is, 564*36 blocks = 20304. It went down to 4 because it used the time from block 20268 to block 20304 as the basis for the diff calculation, and that was several days instead of the target 6 hours. The next one will go up. I'm glad someone here knows there stuff. Phew. Was almost in a panic then. Was too, thanks for the explanation envy2010, didn't think about the multiple.
|
|
|
|
IanFoxley
Legendary
Offline
Activity: 910
Merit: 1000
|
|
January 04, 2014, 09:44:14 PM |
|
I think something is going wrong as my wallet shows I am on block 20325 but latest transaction block on poolerino is 20335
|
|
|
|
vaelrock
|
|
January 04, 2014, 09:45:32 PM |
|
So teamcatcoin is maybe the only pool on the right block chain. We have exactly what's written on the wallet and here : catchain.info/chain/Catcoin
|
|
|
|
Nullu
|
|
January 04, 2014, 09:45:38 PM |
|
I think something is going wrong as my wallet shows I am on block 20325 but latest transaction block on poolerino is 20335
How is poolerino on 20335 but coinium on 20323? Slow to update? Has someone intentionally tried to fork the fork?
|
BTC - 14kYyhhWZwSJFHAjNTtyhRVSu157nE92gF
|
|
|
IanFoxley
Legendary
Offline
Activity: 910
Merit: 1000
|
|
January 04, 2014, 09:46:20 PM |
|
My cat wallet is on 20326 now.
|
|
|
|
|