CaptChadd, It's entirely up to you how you want to proceed, it's your coin. At the very least you need to apply the initial fix so that the client will sync on it's own.
If you plan to make any further changes you really need to specify a set point in the future for those changes to come into effect, you can't just change values globally as this will just reintroduce the syncing issue.
Good luck with your coin.
Topic: [ANN] Extremecoin (EXC) - MANDATORY UPGRADE VERSION 1.5 (Kimoto Gravity Well) - page 23. (Read 97221 times)
October 12, 2013, 11:37:44 AM
October 12, 2013, 10:13:33 AM
And it doesn't matter if the updated code matches to old code exactly, just as long as the outcome is the same then the client will sync and download the whole chain.
Anyways it's a bad habit and should be avoided IMO. 
October 12, 2013, 05:02:15 AM
And it doesn't matter if the updated code matches to old code exactly, just as long as the outcome is the same then the client will sync and download the whole chain.
October 12, 2013, 03:42:35 AM
It's not possible to sync from scratch because of changes to the difficulty algorithm which were applied globally and instantly instead of at a predefined future block.
As far as the current client is concerned the proof of work is wrong for the early blocks because it doesn't match what the code now says.
The only way to fix it so that the client can sync on it's own would be to find out at which block it actually hard forked. Roll back the changes to their original values and then get those same changes to come in at the block it actually hard forked at.
As far as the current client is concerned the proof of work is wrong for the early blocks because it doesn't match what the code now says.
The only way to fix it so that the client can sync on it's own would be to find out at which block it actually hard forked. Roll back the changes to their original values and then get those same changes to come in at the block it actually hard forked at.
Further to this I've created a Pull request which will resolve the issue with syncing the clients without having to rely on manually downloading the blockchain.
Instead of 0.25 * 24 you'd better use 6.
Will be good if we can all come to an agreement as to which would be the best way to go with this code update? It would be good to only have to update this client one more time before the reward drop.
October 11, 2013, 03:24:58 PM
I would really like to avoid another hard fork at this time.
How about we pull the first commit to fix the syncing issue and then I update the OP and website to state what the actual difficulty code does, as it is at the moment?
How about we pull the first commit to fix the syncing issue and then I update the OP and website to state what the actual difficulty code does, as it is at the moment?
October 11, 2013, 02:08:19 PM
Nice. I was wondering about the 1 block retarget when I was looking at the code and thought it was a bit odd. I know it was changed because it was stuck at a high difficulty. It looks like the original code wasn't really doing 2 minute blocks with 4 block retargets, but actually 5 minute blocks and 6 hour (72 block) retargets, maybe thats why it got stuck??
Extremecoin.org says difficulty retarget every 2 blocks.
So who knows what it is supposed to be? CaptChadd?
I think were almost at 12000 as I type this. So 15000 is about 100 hours away around 4 days if the blocks really take 2 minutes. Also the end of the 200 coin block reward is just over a week away if 2 minutes per block holds.
edit: fixed my bad math
Extremecoin.org says difficulty retarget every 2 blocks.
So who knows what it is supposed to be? CaptChadd?
I think were almost at 12000 as I type this. So 15000 is about 100 hours away around 4 days if the blocks really take 2 minutes. Also the end of the 200 coin block reward is just over a week away if 2 minutes per block holds.
edit: fixed my bad math
October 11, 2013, 12:12:42 PM
The original post states retarget every 4 blocks when in fact it is now retargeting every single block (120 / 120 = 1). Also the retarget is currently based solely on the time it took to solve the last block.
It does have code for Balthazar's rolling average which should make it look back 4 retarget intervals but that doesn't kick in until block 15000 as that is what's defined for COINFIX1_BLOCK in src/main.h
For it to match the specifications listed in the first post then I'd suggest a hard fork to make it actually calculate the average every 4 bocks with a 16 block average (4 retarget intervals) at COINFIX1_BLOCK. In order to do this correctly it'd need to switch to actual 4 block retargets at least 16 blocks before it hits COINFIX1_BLOCK (block 14984).
I've therefore submitted an update. If the specs in the first post are actually what are wanted then I highly recommend the pull is accepted and a new client is released ASAP but that's really up to CaptChadd. At the very least my initial commit should be accepted because it fixes the current syncing issue.
It does have code for Balthazar's rolling average which should make it look back 4 retarget intervals but that doesn't kick in until block 15000 as that is what's defined for COINFIX1_BLOCK in src/main.h
For it to match the specifications listed in the first post then I'd suggest a hard fork to make it actually calculate the average every 4 bocks with a 16 block average (4 retarget intervals) at COINFIX1_BLOCK. In order to do this correctly it'd need to switch to actual 4 block retargets at least 16 blocks before it hits COINFIX1_BLOCK (block 14984).
I've therefore submitted an update. If the specs in the first post are actually what are wanted then I highly recommend the pull is accepted and a new client is released ASAP but that's really up to CaptChadd. At the very least my initial commit should be accepted because it fixes the current syncing issue.
October 11, 2013, 10:13:27 AM
It's not possible to sync from scratch because of changes to the difficulty algorithm which were applied globally and instantly instead of at a predefined future block.
As far as the current client is concerned the proof of work is wrong for the early blocks because it doesn't match what the code now says.
The only way to fix it so that the client can sync on it's own would be to find out at which block it actually hard forked. Roll back the changes to their original values and then get those same changes to come in at the block it actually hard forked at.
As far as the current client is concerned the proof of work is wrong for the early blocks because it doesn't match what the code now says.
The only way to fix it so that the client can sync on it's own would be to find out at which block it actually hard forked. Roll back the changes to their original values and then get those same changes to come in at the block it actually hard forked at.
Further to this I've created a Pull request which will resolve the issue with syncing the clients without having to rely on manually downloading the blockchain.
Instead of 0.25 * 24 you'd better use 6.
Agree. Even though it was in the original code that line should be either:
static int64 nTargetTimespan = 6 * 60 * 60; // Extremecoin: 6 hours
or probably better just
static int64 nTargetTimespan = 21600; // Extremecoin: 60 seconds * 60 minutes * 6 hours = 21600 seconds
The last will be slightly more efficient.
But that is a nice fix. Looking forward to the improved client. Thanks to everyone in this community!
EDIT - Also fix the spelling of Exremecoin to Extremecoin please!
October 11, 2013, 06:27:50 AM
It's not possible to sync from scratch because of changes to the difficulty algorithm which were applied globally and instantly instead of at a predefined future block.
As far as the current client is concerned the proof of work is wrong for the early blocks because it doesn't match what the code now says.
The only way to fix it so that the client can sync on it's own would be to find out at which block it actually hard forked. Roll back the changes to their original values and then get those same changes to come in at the block it actually hard forked at.
As far as the current client is concerned the proof of work is wrong for the early blocks because it doesn't match what the code now says.
The only way to fix it so that the client can sync on it's own would be to find out at which block it actually hard forked. Roll back the changes to their original values and then get those same changes to come in at the block it actually hard forked at.
Further to this I've created a Pull request which will resolve the issue with syncing the clients without having to rely on manually downloading the blockchain.
Instead of 0.25 * 24 you'd better use 6.
That part was the original code before it was changed in v1.2, I merely reverted that particular change and dropped const from those lines in order to make them variables instead of constants.
October 11, 2013, 06:25:11 AM
It's not possible to sync from scratch because of changes to the difficulty algorithm which were applied globally and instantly instead of at a predefined future block.
As far as the current client is concerned the proof of work is wrong for the early blocks because it doesn't match what the code now says.
The only way to fix it so that the client can sync on it's own would be to find out at which block it actually hard forked. Roll back the changes to their original values and then get those same changes to come in at the block it actually hard forked at.
As far as the current client is concerned the proof of work is wrong for the early blocks because it doesn't match what the code now says.
The only way to fix it so that the client can sync on it's own would be to find out at which block it actually hard forked. Roll back the changes to their original values and then get those same changes to come in at the block it actually hard forked at.
Further to this I've created a Pull request which will resolve the issue with syncing the clients without having to rely on manually downloading the blockchain.
Instead of 0.25 * 24 you'd better use 6.
Will be good if we can all come to an agreement as to which would be the best way to go with this code update? It would be good to only have to update this client one more time before the reward drop.
October 11, 2013, 06:00:29 AM
It's not possible to sync from scratch because of changes to the difficulty algorithm which were applied globally and instantly instead of at a predefined future block.
As far as the current client is concerned the proof of work is wrong for the early blocks because it doesn't match what the code now says.
The only way to fix it so that the client can sync on it's own would be to find out at which block it actually hard forked. Roll back the changes to their original values and then get those same changes to come in at the block it actually hard forked at.
As far as the current client is concerned the proof of work is wrong for the early blocks because it doesn't match what the code now says.
The only way to fix it so that the client can sync on it's own would be to find out at which block it actually hard forked. Roll back the changes to their original values and then get those same changes to come in at the block it actually hard forked at.
Further to this I've created a Pull request which will resolve the issue with syncing the clients without having to rely on manually downloading the blockchain.
Instead of 0.25 * 24 you'd better use 6.
October 11, 2013, 05:40:55 AM
Hello, I've a little problem when I compile extremecoin-qt. I have clone the github and install dependencies. Maybe I have forget something ?
http://pastebin.com/wUjjK95v
http://pastebin.com/wUjjK95v
October 11, 2013, 05:04:07 AM
It's not possible to sync from scratch because of changes to the difficulty algorithm which were applied globally and instantly instead of at a predefined future block.
As far as the current client is concerned the proof of work is wrong for the early blocks because it doesn't match what the code now says.
The only way to fix it so that the client can sync on it's own would be to find out at which block it actually hard forked. Roll back the changes to their original values and then get those same changes to come in at the block it actually hard forked at.
As far as the current client is concerned the proof of work is wrong for the early blocks because it doesn't match what the code now says.
The only way to fix it so that the client can sync on it's own would be to find out at which block it actually hard forked. Roll back the changes to their original values and then get those same changes to come in at the block it actually hard forked at.
Further to this I've created a Pull request which will resolve the issue with syncing the clients without having to rely on manually downloading the blockchain.
Thanks for this.
I will merge this pull reqest over the weekend and compile a Windows client for everyone, add it to the OP and website.
October 10, 2013, 11:31:00 PM
It's not possible to sync from scratch because of changes to the difficulty algorithm which were applied globally and instantly instead of at a predefined future block.
As far as the current client is concerned the proof of work is wrong for the early blocks because it doesn't match what the code now says.
The only way to fix it so that the client can sync on it's own would be to find out at which block it actually hard forked. Roll back the changes to their original values and then get those same changes to come in at the block it actually hard forked at.
As far as the current client is concerned the proof of work is wrong for the early blocks because it doesn't match what the code now says.
The only way to fix it so that the client can sync on it's own would be to find out at which block it actually hard forked. Roll back the changes to their original values and then get those same changes to come in at the block it actually hard forked at.
Further to this I've created a Pull request which will resolve the issue with syncing the clients without having to rely on manually downloading the blockchain.
October 10, 2013, 06:47:55 PM
Wallet now sync with the network
I receive EXC in wallet.
Thx.
I receive EXC in wallet.
Thx.
October 10, 2013, 03:34:51 PM
Download the blockchain.
Once you download the blockchain, extract it to your Extremecoin profile folder.
On windows this is at C:\Users\\AppData\Roaming\Extremecoin.
Then let your client sync up. Once it finishes you should see the transaction in your wallet.
Use the upto date blockchain so you can catch up and start solo mining with the new client.
https://www.dropbox.com/s/aqjpkcqkd5akrhb/Extremecoin%20Blockchain.zip
Thanks for holding in there, I will get this all sorted.
https://www.dropbox.com/s/aqjpkcqkd5akrhb/Extremecoin%20Blockchain.zip
Thanks for holding in there, I will get this all sorted.
Once you download the blockchain, extract it to your Extremecoin profile folder.
On windows this is at C:\Users\
Then let your client sync up. Once it finishes you should see the transaction in your wallet.
October 10, 2013, 02:54:05 PM
coinEX.pw sent to 21100 EXC in my address: PGF6uFvkstBgXngDcKJKT7H14wZRv6a3wf , but did not go in wallet
"txid" : "5ee5adab8d9d2f6b16ee519a404fc75edb011f281dd7b3a62d168751689accac"
How do I get my EXC in wallet ?
"txid" : "5ee5adab8d9d2f6b16ee519a404fc75edb011f281dd7b3a62d168751689accac"
How do I get my EXC in wallet ?
October 10, 2013, 02:29:58 PM
It's not possible to sync from scratch because of changes to the difficulty algorithm which were applied globally and instantly instead of at a predefined future block.
As far as the current client is concerned the proof of work is wrong for the early blocks because it doesn't match what the code now says.
The only way to fix it so that the client can sync on it's own would be to find out at which block it actually hard forked. Roll back the changes to their original values and then get those same changes to come in at the block it actually hard forked at.
As far as the current client is concerned the proof of work is wrong for the early blocks because it doesn't match what the code now says.
The only way to fix it so that the client can sync on it's own would be to find out at which block it actually hard forked. Roll back the changes to their original values and then get those same changes to come in at the block it actually hard forked at.
October 10, 2013, 02:28:42 PM
I have version 1.2 wallet extremecoin but I do not sync with the network, trying to sync wallet
but stay locked to 11636 blocks.
I withdraw 21100 EXC from a pool but do not get extremecoin in wallet address.
What can I do to get EXC in wallet address ?
Thx.
but stay locked to 11636 blocks.
I withdraw 21100 EXC from a pool but do not get extremecoin in wallet address.
What can I do to get EXC in wallet address ?
Thx.
October 10, 2013, 02:08:56 PM
Extremecoin has now been added to the Iphone App Coin Ticker.
More services to come.
More services to come.
Jump to: