JohnCar (OP)
|
|
June 18, 2013, 04:10:57 PM Last edit: June 19, 2013, 07:55:18 PM by JohnCar |
|
Hello all just wanted to let everyone know there is a new client for PhenixCoin ** PLEASE UPDATE YOUR CLIENTS ** - Version 6.4.7 is now available, please download it before block 46500. You can download the client from here http://phenixcoin.comChanges that have been implemented are: Difficultly changes every 480 blocks max change is 80%. We have also added checkpoints as well. Please help spread the word of the new client for PhenixCoin. Thank you for your support and happy mining! Thanks John
|
TIT coming soon..............
|
|
|
elambert
Legendary
Offline
Activity: 1696
Merit: 1008
|
|
June 18, 2013, 04:12:54 PM |
|
I have a qt wallet for my Mac downloaded from here. Do i need to do anything? Looks like u guys are doing great work. Happy to beinvested in this coin :-)
|
|
|
|
JohnCar (OP)
|
|
June 18, 2013, 04:17:07 PM |
|
I have a qt wallet for my Mac downloaded from here. Do i need to do anything? Looks like u guys are doing great work. Happy to beinvested in this coin :-)
Just waiting for Iamatrix to get back online which will be shortly. I wanna ask him before i give you a answer. Thanks for the support!
|
TIT coming soon..............
|
|
|
|
bubbers214
Newbie
Offline
Activity: 49
Merit: 0
|
|
June 18, 2013, 04:27:00 PM |
|
Which block number will the difficulty adjustment be occurring?
|
|
|
|
JohnCar (OP)
|
|
June 18, 2013, 04:28:33 PM |
|
Which block number will the difficulty adjustment be occurring?
46500
|
TIT coming soon..............
|
|
|
MaGNeT
Legendary
Offline
Activity: 1526
Merit: 1002
Waves | 3PHMaGNeTJfqFfD4xuctgKdoxLX188QM8na
|
|
June 18, 2013, 04:28:45 PM |
|
Which block number will the difficulty adjustment be occurring?
46,500 It's all in the OP
|
|
|
|
bubbers214
Newbie
Offline
Activity: 49
Merit: 0
|
|
June 18, 2013, 04:30:51 PM |
|
I guess I should learn how to read a little better
|
|
|
|
Eb0la
|
|
June 18, 2013, 04:35:26 PM |
|
Awesome work! updated my side
|
|
|
|
iamatrix
|
|
June 18, 2013, 04:40:46 PM |
|
I have a qt wallet for my Mac downloaded from here. Do i need to do anything? Looks like u guys are doing great work. Happy to beinvested in this coin :-)
no you will have to update.. unfortunately I do not have access to MAC or I would compile it.
|
PhenixEx cryptocurrency exchange | Lifetime lower trading fees? Sign up here! | Let others sign up with your referral link and receive 25% of their trading fees!
|
|
|
MaGNeT
Legendary
Offline
Activity: 1526
Merit: 1002
Waves | 3PHMaGNeTJfqFfD4xuctgKdoxLX188QM8na
|
|
June 18, 2013, 05:08:05 PM |
|
I have a qt wallet for my Mac downloaded from here. Do i need to do anything? Looks like u guys are doing great work. Happy to beinvested in this coin :-)
no you will have to update.. unfortunately I do not have access to MAC or I would compile it. Maybe you could PM maxpower? https://bitcointalk.org/index.php?topic=216672.0
|
|
|
|
iamatrix
|
|
June 18, 2013, 05:13:26 PM |
|
I have a qt wallet for my Mac downloaded from here. Do i need to do anything? Looks like u guys are doing great work. Happy to beinvested in this coin :-)
no you will have to update.. unfortunately I do not have access to MAC or I would compile it. Maybe you could PM maxpower? https://bitcointalk.org/index.php?topic=216672.0Done.... thanks...
|
PhenixEx cryptocurrency exchange | Lifetime lower trading fees? Sign up here! | Let others sign up with your referral link and receive 25% of their trading fees!
|
|
|
DonDe
Newbie
Offline
Activity: 56
Merit: 0
|
|
June 18, 2013, 05:15:53 PM |
|
need a good working pool for PXC
|
|
|
|
MaGNeT
Legendary
Offline
Activity: 1526
Merit: 1002
Waves | 3PHMaGNeTJfqFfD4xuctgKdoxLX188QM8na
|
|
June 18, 2013, 05:45:03 PM |
|
|
|
|
|
aysyr
|
|
June 18, 2013, 05:55:21 PM |
|
I've just updated Glad to be hearing from you guys the past couple of days. Excited for your upcoming releases haha. Feels good to be one of the few current supporters of Phenixcoin before it goes big!
|
|
|
|
elambert
Legendary
Offline
Activity: 1696
Merit: 1008
|
|
June 18, 2013, 06:18:07 PM |
|
I have a qt wallet for my Mac downloaded from here. Do i need to do anything? Looks like u guys are doing great work. Happy to beinvested in this coin :-)
no you will have to update.. unfortunately I do not have access to MAC or I would compile it. Maybe you could PM maxpower? https://bitcointalk.org/index.php?topic=216672.0Done.... thanks... Maxpower said he is traveling this week when I communicated with him on an unrelated subject. Please let me know what he says...
|
|
|
|
elambert
Legendary
Offline
Activity: 1696
Merit: 1008
|
|
June 18, 2013, 06:21:20 PM |
|
I have a qt wallet for my Mac downloaded from here. Do i need to do anything? Looks like u guys are doing great work. Happy to beinvested in this coin :-)
no you will have to update.. unfortunately I do not have access to MAC or I would compile it. Maybe you could PM maxpower? https://bitcointalk.org/index.php?topic=216672.0Done.... thanks... Should I move my coin to an exchange until my wallet can get updated? How much time do I have, no idea what block we are on...
|
|
|
|
feeleep
Legendary
Offline
Activity: 1197
Merit: 1000
|
|
June 18, 2013, 06:22:55 PM |
|
Updated client on my pool. http://pxc.coinmine.plPool has proportional payout system so you will get instant payouts after each block - start mining!
|
|
|
|
chondrite
|
|
June 18, 2013, 06:41:45 PM |
|
Thanks for the update!
|
|
|
|
aysyr
|
|
June 18, 2013, 07:01:35 PM |
|
I have a qt wallet for my Mac downloaded from here. Do i need to do anything? Looks like u guys are doing great work. Happy to beinvested in this coin :-)
no you will have to update.. unfortunately I do not have access to MAC or I would compile it. Maybe you could PM maxpower? https://bitcointalk.org/index.php?topic=216672.0Done.... thanks... Should I move my coin to an exchange until my wallet can get updated? How much time do I have, no idea what block we are on... Highlight the green checkmark on the bottom right of your wallet and it'll tell you what block it's on
|
|
|
|
MaGNeT
Legendary
Offline
Activity: 1526
Merit: 1002
Waves | 3PHMaGNeTJfqFfD4xuctgKdoxLX188QM8na
|
|
June 18, 2013, 07:04:36 PM |
|
I have a qt wallet for my Mac downloaded from here. Do i need to do anything? Looks like u guys are doing great work. Happy to beinvested in this coin :-)
no you will have to update.. unfortunately I do not have access to MAC or I would compile it. Maybe you could PM maxpower? https://bitcointalk.org/index.php?topic=216672.0Done.... thanks... Should I move my coin to an exchange until my wallet can get updated? How much time do I have, no idea what block we are on... If you have a backup of your wallet.dat you're fine Don't panic
|
|
|
|
elambert
Legendary
Offline
Activity: 1696
Merit: 1008
|
|
June 18, 2013, 08:19:49 PM |
|
I have a qt wallet for my Mac downloaded from here. Do i need to do anything? Looks like u guys are doing great work. Happy to beinvested in this coin :-)
no you will have to update.. unfortunately I do not have access to MAC or I would compile it. Maybe you could PM maxpower? https://bitcointalk.org/index.php?topic=216672.0Done.... thanks... Should I move my coin to an exchange until my wallet can get updated? How much time do I have, no idea what block we are on... If you have a backup of your wallet.dat you're fine Don't panic Unfortunately I have not had success backing up on the Mac What block are we on? I am at work
|
|
|
|
|
iamatrix
|
|
June 19, 2013, 01:57:54 AM Last edit: June 19, 2013, 02:28:36 AM by iamatrix |
|
lol I forgot about that URL... we've been looking for a decent domain, but that will work.. how about 1hr ok I installed it, John will get it setup, while I finish off the exchange..
|
PhenixEx cryptocurrency exchange | Lifetime lower trading fees? Sign up here! | Let others sign up with your referral link and receive 25% of their trading fees!
|
|
|
rqdxrocket
|
|
June 19, 2013, 11:09:47 AM |
|
lol I forgot about that URL... we've been looking for a decent domain, but that will work.. how about 1hr ok I installed it, John will get it setup, while I finish off the exchange.. I see that is in now functional - thx
|
|
|
|
JohnCar (OP)
|
|
June 19, 2013, 11:12:10 AM |
|
lol I forgot about that URL... we've been looking for a decent domain, but that will work.. how about 1hr ok I installed it, John will get it setup, while I finish off the exchange.. I see that is in now functional - thx The basics are there so feel free to join.
|
TIT coming soon..............
|
|
|
|
weav
Sr. Member
Offline
Activity: 350
Merit: 250
- "Bitcore (BTX) - Airdrops every Monday"
|
|
June 19, 2013, 01:27:05 PM |
|
Do you guys intend fixing the syncing bug in the Linux version?
|
|
|
|
iamatrix
|
|
June 19, 2013, 01:42:30 PM |
|
Do you guys intend fixing the syncing bug in the Linux version? Yes.. I am trying to duplicate your issue, have not been able to duplicate it yet. I have it compiled on Ubuntu and CentOs with no issues..
|
PhenixEx cryptocurrency exchange | Lifetime lower trading fees? Sign up here! | Let others sign up with your referral link and receive 25% of their trading fees!
|
|
|
weav
Sr. Member
Offline
Activity: 350
Merit: 250
- "Bitcore (BTX) - Airdrops every Monday"
|
|
June 19, 2013, 01:48:47 PM |
|
Do you guys intend fixing the syncing bug in the Linux version? Yes.. I am trying to duplicate your issue, have not been able to duplicate it yet. I have it compiled on Ubuntu and CentOs with no issues.. Oh, weird, thanks for looking into it. Is there any debug info I could gather and send you?
|
|
|
|
|
weav
Sr. Member
Offline
Activity: 350
Merit: 250
- "Bitcore (BTX) - Airdrops every Monday"
|
|
June 19, 2013, 04:08:59 PM |
|
I guess I found the relevant error in the output of ./phenixcoin-qt -printtoconsole> received block 240ba90dc2981bed8761 ERROR: AcceptBlock() : incorrect proof of work ERROR: ProcessBlock() : AcceptBlock FAILED Note that block 240ba90dc2981bed8761 is indeed block 2400, the block where sync gets stuck an the old difficulty retarget: http://explorer.phenixcoin.com/block/240ba90dc2981bed8761cc88977843f677f07cc12811cbb8bee981c843058c73
|
|
|
|
iamatrix
|
|
June 19, 2013, 04:17:36 PM |
|
I am looking at this right now..
|
PhenixEx cryptocurrency exchange | Lifetime lower trading fees? Sign up here! | Let others sign up with your referral link and receive 25% of their trading fees!
|
|
|
weav
Sr. Member
Offline
Activity: 350
Merit: 250
- "Bitcore (BTX) - Airdrops every Monday"
|
|
June 19, 2013, 05:51:05 PM Last edit: June 19, 2013, 06:09:31 PM by weav |
|
I added some debug output in src/main.cpp: // Check proof of work if (nBits != GetNextWorkRequired(pindexPrev, this)) { printf("pindexPrev: %u\n", pindexPrev); printf("nBits: %u\n", nBits); printf("GetNextWorkRequired(pindexPrev, this): %u\n", GetNextWorkRequired(pindexPrev, this)); return DoS(100, error("AcceptBlock() : incorrect proof of work")); } and compiled it again, now I get: received block 240ba90dc2981bed8761 pindexPrev: 40149344 nBits: 504365055 GetNextWorkRequired(pindexPrev, this): 504365040 ERROR: AcceptBlock() : incorrect proof of work ERROR: ProcessBlock() : AcceptBlock FAILED EDIT: not sure if relevant but after running it several times I noticed the value of pindexPrev (the "prev block index" according to the comments, sounds pretty static to me considering that my wallet is stuck at block 2400) seems to vary randomly: pindexPrev: 44792240 .. pindexPrev: 29553056 .. pindexPrev: 41622112 .. pindexPrev: 51966576 .. pindexPrev: 41933584 Both nBits and GetNextWorkRequired(pindexPrev, this) are static across different runs.
|
|
|
|
|
MaGNeT
Legendary
Offline
Activity: 1526
Merit: 1002
Waves | 3PHMaGNeTJfqFfD4xuctgKdoxLX188QM8na
|
|
June 19, 2013, 08:00:38 PM |
|
Nobody is perfect edit: I see it's updated at http://www.phenixcoin.com
|
|
|
|
weav
Sr. Member
Offline
Activity: 350
Merit: 250
- "Bitcore (BTX) - Airdrops every Monday"
|
|
June 19, 2013, 08:06:56 PM |
|
Great! That fixed it, wallet syncing properly now! While trying to debug the issue on my system I found another apparent dissonance in the code in src/main.cpp: 840 static const int64 nTargetTimespan = 0.5 * 24 * 60 * 60; // Phenixcoin: 2.5 days 841 static const int64 nTargetSpacing = 1.5 * 60; // Phenixcoin: 1.5 minutes .. 889 int64 nTargetTimespanCurrent = fNewDifficultyProtocol? nTargetTimespan : (nTargetTimespan*4); 890 int64 nInterval = nTargetTimespanCurrent / nTargetSpacing; Ignoring the comments (which don't fully match the code and are possibly just leftovers from the feathercoin repo or something) and assuming nInterval denotes the number of blocks until difficulty retarget we correctly get: nInterval = (0.5 * 24 * 60 * 60) / (1.5 * 60) = 480 which is the number of blocks for the new difficulty protocol, but for the old protocol we get: nInterval = ((0.5 * 24 * 60 * 60) * 4) / (1.5 * 60) = 1920 which isn't the 2400 blocks as specified in the original forum announcement and on phenixcoin.com... (it would be for int64 nTargetTimespanCurrent = fNewDifficultyProtocol? nTargetTimespan : (nTargetTimespan*5);) Am I missing something?
|
|
|
|
TheFuneral
|
|
June 19, 2013, 08:20:37 PM |
|
Updated client on my pool. http://pxc.coinmine.plPool has proportional payout system so you will get instant payouts after each block - start mining! is your pool still up?
|
|
|
|
iamatrix
|
|
June 19, 2013, 08:22:13 PM |
|
Great! That fixed it, wallet syncing properly now! While trying to debug the issue on my system I found another apparent dissonance in the code in src/main.cpp: 840 static const int64 nTargetTimespan = 0.5 * 24 * 60 * 60; // Phenixcoin: 2.5 days 841 static const int64 nTargetSpacing = 1.5 * 60; // Phenixcoin: 1.5 minutes .. 889 int64 nTargetTimespanCurrent = fNewDifficultyProtocol? nTargetTimespan : (nTargetTimespan*4); 890 int64 nInterval = nTargetTimespanCurrent / nTargetSpacing; Ignoring the comments (which don't fully match the code and are possibly just leftovers from the feathercoin repo or something) and assuming nInterval denotes the number of blocks until difficulty retarget we correctly get: nInterval = (0.5 * 24 * 60 * 60) / (1.5 * 60) = 480 which is the number of blocks for the new difficulty protocol, but for the old protocol we get: nInterval = ((0.5 * 24 * 60 * 60) * 4) / (1.5 * 60) = 1920 which isn't the 2400 blocks as specified in the original forum announcement and on phenixcoin.com... (it would be for int64 nTargetTimespanCurrent = fNewDifficultyProtocol? nTargetTimespan : (nTargetTimespan*5);) Am I missing something? that was not the old protocal ... the old was 2.5 * 24
|
PhenixEx cryptocurrency exchange | Lifetime lower trading fees? Sign up here! | Let others sign up with your referral link and receive 25% of their trading fees!
|
|
|
nawazish1
Sr. Member
Offline
Activity: 462
Merit: 250
PXC Research Team
|
|
June 19, 2013, 08:23:53 PM |
|
Updated client on my pool. http://pxc.coinmine.plPool has proportional payout system so you will get instant payouts after each block - start mining! is your pool still up? You can mine in the official pools now I think they are good now. http://phoen01.phenixpool.com/http://amst01.phenixpool.com/
|
PXC: PmfFgdwwcXPa1QUmtVJevdPfHhmhztHHCv BTC: 1P22tVABsd85L7kkpTmohCv5vK2BypFz3H Phoenixcoin (PXC), a decentralised open source digital currency.
|
|
|
weav
Sr. Member
Offline
Activity: 350
Merit: 250
- "Bitcore (BTX) - Airdrops every Monday"
|
|
June 19, 2013, 08:31:07 PM |
|
Great! That fixed it, wallet syncing properly now! While trying to debug the issue on my system I found another apparent dissonance in the code in src/main.cpp: 840 static const int64 nTargetTimespan = 0.5 * 24 * 60 * 60; // Phenixcoin: 2.5 days 841 static const int64 nTargetSpacing = 1.5 * 60; // Phenixcoin: 1.5 minutes .. 889 int64 nTargetTimespanCurrent = fNewDifficultyProtocol? nTargetTimespan : (nTargetTimespan*4); 890 int64 nInterval = nTargetTimespanCurrent / nTargetSpacing; Ignoring the comments (which don't fully match the code and are possibly just leftovers from the feathercoin repo or something) and assuming nInterval denotes the number of blocks until difficulty retarget we correctly get: nInterval = (0.5 * 24 * 60 * 60) / (1.5 * 60) = 480 which is the number of blocks for the new difficulty protocol, but for the old protocol we get: nInterval = ((0.5 * 24 * 60 * 60) * 4) / (1.5 * 60) = 1920 which isn't the 2400 blocks as specified in the original forum announcement and on phenixcoin.com... (it would be for int64 nTargetTimespanCurrent = fNewDifficultyProtocol? nTargetTimespan : (nTargetTimespan*5);) Am I missing something? that was not the old protocal ... the old was 2.5 * 24 Yes that is my point, currently the code does: 0.5 * (24 * 60 * 60) * 4 == 2.0 * (24 * 60 * 60)but shouldn't it be: 0.5 * (24 * 60 * 60) * 5 == 2.5 * (24 * 60 * 60) ?
|
|
|
|
AquaMan
Newbie
Offline
Activity: 42
Merit: 0
|
|
June 19, 2013, 08:58:42 PM |
|
Updated client on my pool. http://pxc.coinmine.plPool has proportional payout system so you will get instant payouts after each block - start mining! is your pool still up? Several are up now...
|
|
|
|
iamatrix
|
|
June 19, 2013, 09:07:37 PM |
|
Great! That fixed it, wallet syncing properly now! While trying to debug the issue on my system I found another apparent dissonance in the code in src/main.cpp: 840 static const int64 nTargetTimespan = 0.5 * 24 * 60 * 60; // Phenixcoin: 2.5 days 841 static const int64 nTargetSpacing = 1.5 * 60; // Phenixcoin: 1.5 minutes .. 889 int64 nTargetTimespanCurrent = fNewDifficultyProtocol? nTargetTimespan : (nTargetTimespan*4); 890 int64 nInterval = nTargetTimespanCurrent / nTargetSpacing; Ignoring the comments (which don't fully match the code and are possibly just leftovers from the feathercoin repo or something) and assuming nInterval denotes the number of blocks until difficulty retarget we correctly get: nInterval = (0.5 * 24 * 60 * 60) / (1.5 * 60) = 480 which is the number of blocks for the new difficulty protocol, but for the old protocol we get: nInterval = ((0.5 * 24 * 60 * 60) * 4) / (1.5 * 60) = 1920 which isn't the 2400 blocks as specified in the original forum announcement and on phenixcoin.com... (it would be for int64 nTargetTimespanCurrent = fNewDifficultyProtocol? nTargetTimespan : (nTargetTimespan*5);) Am I missing something? that was not the old protocal ... the old was 2.5 * 24 Yes that is my point, currently the code does: 0.5 * (24 * 60 * 60) * 4 == 2.0 * (24 * 60 * 60)but shouldn't it be: 0.5 * (24 * 60 * 60) * 5 == 2.5 * (24 * 60 * 60) ? You looking at 6.4.5 code.. 6.4.7 is (5 * 24 * 60 * 60) / 8
|
PhenixEx cryptocurrency exchange | Lifetime lower trading fees? Sign up here! | Let others sign up with your referral link and receive 25% of their trading fees!
|
|
|
feeleep
Legendary
Offline
Activity: 1197
Merit: 1000
|
|
June 19, 2013, 09:29:25 PM |
|
Updated client on my pool. http://pxc.coinmine.plPool has proportional payout system so you will get instant payouts after each block - start mining! is your pool still up? updated client on my pool to the latest - you are welcome to start mining! http://pxc.coinmine.pl:9095
|
|
|
|
weav
Sr. Member
Offline
Activity: 350
Merit: 250
- "Bitcore (BTX) - Airdrops every Monday"
|
|
June 19, 2013, 09:34:53 PM Last edit: June 19, 2013, 10:13:12 PM by weav |
|
that was not the old protocal ... the old was 2.5 * 24
Yes that is my point, currently the code does: 0.5 * (24 * 60 * 60) * 4 == 2.0 * (24 * 60 * 60)but shouldn't it be: 0.5 * (24 * 60 * 60) * 5 == 2.5 * (24 * 60 * 60) ? You looking at 6.4.5 code.. 6.4.7 is (5 * 24 * 60 * 60) / 8 Oh right, so you've addressed that already together with the sync issue (or it was actually causing it). Now I'm seeing it: https://github.com/phenixcoin/Phenixcoin/commit/075d96d75873007d3d8997204cfaa2f3bf7507c2I was only looking at the most recent commit earlier: https://github.com/phenixcoin/Phenixcoin/commit/48e6768f2bae47df679244108962fb67b1b89809But actually I think this introduces an even more severe bug because now it affects the future blockchain instead of just the verification of the existing chain prior to the difficulty protocol change. Look at the current code in the repo https://github.com/phenixcoin/Phenixcoin/blob/master/src/main.cpp: 840 static const int64 nTargetTimespan = (5 * 24 * 60 * 60) / 8; // Phenixcoin: 2.5 days 841 static const int64 nTargetSpacing = 1.5 * 60; // Phenixcoin: 1.5 minutes .. 886 int64 nTargetTimespanCurrent = fNewDifficultyProtocol? nTargetTimespan : (nTargetTimespan*4); 887 int64 nInterval = nTargetTimespanCurrent / nTargetSpacing; Apart from the comment still not matching the code: (5 * 24 * 60 * 60) / 8 == (5/8) * (24 * 60 * 60) == 0.625 * (24 * 60 * 60) == 0.625 daysthe far more serious issue is that now the nInterval isn't 480 anymore if fNewDifficultyProtocol is true, that is if we are past block 46500 where the difficulty protocol adjustment applies. Now it's basically the other way around, for the old protocol we do correctly get: nInterval = (((5 * 24 * 60 * 60) / 8) * 4) / (1.5 * 60) = 2400 which is the number of blocks until difficulty retarget as specified in the original forum announcement and on phenixcoin.com, and which in part explains why the block verification during the wallet sync doesn't fail anymore for retarget blocks which caused the sync to get stuck. But now for the new protocol we get: nInterval = ((5 * 24 * 60 * 60) / 8) / (1.5 * 60) = 600 which isn't the 480 blocks as defined in the recent difficulty protocol fix! I guess this should be fixed urgently before the next difficulty retarget occursAnd I still think this would fully fix it: 840 static const int64 nTargetTimespan = 0.5 * 24 * 60 * 60; // Phenixcoin: 12 hours 841 static const int64 nTargetSpacing = 1.5 * 60; // Phenixcoin: 1.5 minutes .. 886 int64 nTargetTimespanCurrent = fNewDifficultyProtocol? nTargetTimespan : (nTargetTimespan*5); // NOTE THE *5 HERE 887 int64 nInterval = nTargetTimespanCurrent / nTargetSpacing;
|
|
|
|
MaGNeT
Legendary
Offline
Activity: 1526
Merit: 1002
Waves | 3PHMaGNeTJfqFfD4xuctgKdoxLX188QM8na
|
|
June 19, 2013, 10:15:48 PM |
|
that was not the old protocal ... the old was 2.5 * 24
Yes that is my point, currently the code does: 0.5 * (24 * 60 * 60) * 4 == 2.0 * (24 * 60 * 60)but shouldn't it be: 0.5 * (24 * 60 * 60) * 5 == 2.5 * (24 * 60 * 60) ? You looking at 6.4.5 code.. 6.4.7 is (5 * 24 * 60 * 60) / 8 Oh right, so you've addressed that already together with the sync issue (or it was actually causing it). Now I'm seeing it: https://github.com/phenixcoin/Phenixcoin/commit/075d96d75873007d3d8997204cfaa2f3bf7507c2I was only looking at the most recent commit earlier: https://github.com/phenixcoin/Phenixcoin/commit/48e6768f2bae47df679244108962fb67b1b89809But actually I think this introduces an even more severe bug because now it affects the future blockchain instead of just the verification of the existing chain prior to the difficulty protocol change. Look at the current code in the repo https://github.com/phenixcoin/Phenixcoin/blob/master/src/main.cpp: 840 static const int64 nTargetTimespan = (5 * 24 * 60 * 60) / 8; // Phenixcoin: 2.5 days 841 static const int64 nTargetSpacing = 1.5 * 60; // Phenixcoin: 1.5 minutes .. 886 int64 nTargetTimespanCurrent = fNewDifficultyProtocol? nTargetTimespan : (nTargetTimespan*4); 887 int64 nInterval = nTargetTimespanCurrent / nTargetSpacing; Apart from the comment still not matching the code: (5 * 24 * 60 * 60) / 8 == (5/8) * (24 * 60 * 60) == 0.625 * (24 * 60 * 60) == 0.625 daysthe far more serious issue is that now the nInterval isn't 480 anymore if fNewDifficultyProtocol is true, that is if we are past block 46500 where the difficulty protocol adjustment applies. Now it's basically the other way around, for the old protocol we do correctly get: nInterval = (((5 * 24 * 60 * 60) / 8) * 4) / (1.5 * 60) = 2400 which is the number of blocks until difficulty retarget as specified in the original forum announcement and on phenixcoin.com, and which in part explains why the block verification during the wallet sync doesn't fail anymore for retarget blocks which caused the sync to get stuck. But now for the new protocol we get: nInterval = ((5 * 24 * 60 * 60) / 8) / (1.5 * 60) = 600 which isn't the 480 blocks as defined in the recent difficulty protocol fix! I guess this should be fixed urgently before the next difficulty retarget occursAnd I still think this would fully fix it: 840 static const int64 nTargetTimespan = 0.5 * 24 * 60 * 60; // Phenixcoin: 12 hours 841 static const int64 nTargetSpacing = 1.5 * 60; // Phenixcoin: 1.5 minutes .. 886 int64 nTargetTimespanCurrent = fNewDifficultyProtocol? nTargetTimespan : (nTargetTimespan*5); // NOTE THE *5 HERE 887 int64 nInterval = nTargetTimespanCurrent / nTargetSpacing; Don't understand all you say but if it needs to be fixed, I guess it needs to be fixed Iamatrix needs a twin-brother
|
|
|
|
iamatrix
|
|
June 19, 2013, 10:29:06 PM |
|
840 static const int64 nTargetTimespan = 0.5 * 24 * 60 * 60; // Phenixcoin: 12 hours 841 static const int64 nTargetSpacing = 1.5 * 60; // Phenixcoin: 1.5 minutes .. 886 int64 nTargetTimespanCurrent = fNewDifficultyProtocol? nTargetTimespan : (nTargetTimespan*5); // NOTE THE *5 HERE 887 int64 nInterval = nTargetTimespanCurrent / nTargetSpacing; Yes, with the last update I made, it changed the diff change at 600 blocks instead of 480, and increased the time from 12hrs to 15hrs.. The 46500 marker came up way faster then I expected, I was thinking late thursday, early friday for the change over.. I will talk it over with John and see what we come up with.
|
PhenixEx cryptocurrency exchange | Lifetime lower trading fees? Sign up here! | Let others sign up with your referral link and receive 25% of their trading fees!
|
|
|
weav
Sr. Member
Offline
Activity: 350
Merit: 250
- "Bitcore (BTX) - Airdrops every Monday"
|
|
June 19, 2013, 10:38:14 PM |
|
840 static const int64 nTargetTimespan = 0.5 * 24 * 60 * 60; // Phenixcoin: 12 hours 841 static const int64 nTargetSpacing = 1.5 * 60; // Phenixcoin: 1.5 minutes .. 886 int64 nTargetTimespanCurrent = fNewDifficultyProtocol? nTargetTimespan : (nTargetTimespan*5); // NOTE THE *5 HERE 887 int64 nInterval = nTargetTimespanCurrent / nTargetSpacing; Yes, with the last update I made, it changed the diff change at 600 blocks instead of 480, and increased the time from 12hrs to 15hrs.. The 46500 marker came up way faster then I expected, I was thinking late thursday, early friday for the change over.. I will talk it over with John and see what we come up with. Oh, so this was intentional I was assuming it must be a bug because it wasn't mentioned anywhere in the announcements or on phenixcoin.com I kinda like the "symmetry" between block reward halves every 840k blocks and difficulty changes every 480 blocks but by all means what's best for the coin!
|
|
|
|
weav
Sr. Member
Offline
Activity: 350
Merit: 250
- "Bitcore (BTX) - Airdrops every Monday"
|
|
June 19, 2013, 11:00:19 PM Last edit: June 19, 2013, 11:32:17 PM by weav |
|
Just for general transparency, can you please explain why users of the binaries you guys provide were unaffected by the bug which just got fixed in the official code repository on https://github.com/phenixcoin/Phenixcoin ? Apparently the issue only occured for linux users who compiled their own binaries from the public source, and noticeably so because the wallet sync got completely stuck. I cannot imagine a setting or environment where the former code wouldn't cause this behavior. Are you compiling the binaries you release on phenixcoin.com from a separate codebase which differs from the repo on github, and if so, why? Thanks
|
|
|
|
iamatrix
|
|
June 19, 2013, 11:15:44 PM |
|
Just for general transparency, can you please explain why users of the binaries you guys provide were unaffected by the bug which just got fixed in the official code repository on https://github.com/phenixcoin/Phenixcoin ? Apparently the issue only occured for linux users who compiled their own binaries from the public source, and noticeably so because the wallet sync got completely stuck. I cannot imagine a setting or environment where the former code wouldn't cause this behavior. Are you compiling the binaries you release on phenixcoin.com from a separate codebase which differs from the repo on github, and if so, why? Thanks I was kind of wondering the same thing as well, I delete my block chain and it downloaded fine.. its not a different code base. Most people where not effected because they already had the block chain and it was stalling on a block with a diff change. trust me, I will be looking into why the windows binary worked.. its pretty easy to setup a mingw compile env for windows, grab the code for 6.4.5 and try it.. we have full transparency with the coin..
|
PhenixEx cryptocurrency exchange | Lifetime lower trading fees? Sign up here! | Let others sign up with your referral link and receive 25% of their trading fees!
|
|
|
weav
Sr. Member
Offline
Activity: 350
Merit: 250
- "Bitcore (BTX) - Airdrops every Monday"
|
|
June 19, 2013, 11:29:30 PM |
|
Just for general transparency, can you please explain why users of the binaries you guys provide were unaffected by the bug which just got fixed in the official code repository on https://github.com/phenixcoin/Phenixcoin ? Apparently the issue only occured for linux users who compiled their own binaries from the public source, and noticeably so because the wallet sync got completely stuck. I cannot imagine a setting or environment where the former code wouldn't cause this behavior. Are you compiling the binaries you release on phenixcoin.com from a separate codebase which differs from the repo on github, and if so, why? Thanks I was kind of wondering the same thing as well, I delete my block chain and it downloaded fine.. its not a different code base. Most people where not effected because they already had the block chain and it was stalling on a block with a diff change. trust me, I will be looking into why the windows binary worked.. its pretty easy to setup a mingw compile env for windows, grab the code for 6.4.5 and try it.. we have full transparency with the coin.. Thanks, sounds reasonable, in particular that most people probably already had the complete blockchain with the latest retarget block in their wallets. Must be some really weird windows side effect then.
|
|
|
|
iamatrix
|
|
June 19, 2013, 11:37:31 PM |
|
Just for general transparency, can you please explain why users of the binaries you guys provide were unaffected by the bug which just got fixed in the official code repository on https://github.com/phenixcoin/Phenixcoin ? Apparently the issue only occured for linux users who compiled their own binaries from the public source, and noticeably so because the wallet sync got completely stuck. I cannot imagine a setting or environment where the former code wouldn't cause this behavior. Are you compiling the binaries you release on phenixcoin.com from a separate codebase which differs from the repo on github, and if so, why? Thanks I was kind of wondering the same thing as well, I delete my block chain and it downloaded fine.. its not a different code base. Most people where not effected because they already had the block chain and it was stalling on a block with a diff change. trust me, I will be looking into why the windows binary worked.. its pretty easy to setup a mingw compile env for windows, grab the code for 6.4.5 and try it.. we have full transparency with the coin.. Thanks, sounds reasonable, in particular that most people probably already had the complete blockchain with the latest retarget block in their wallets. Must be some really weird windows side effect then. Ya but I still want to know why..
|
PhenixEx cryptocurrency exchange | Lifetime lower trading fees? Sign up here! | Let others sign up with your referral link and receive 25% of their trading fees!
|
|
|
weav
Sr. Member
Offline
Activity: 350
Merit: 250
- "Bitcore (BTX) - Airdrops every Monday"
|
|
June 19, 2013, 11:53:10 PM |
|
Just for general transparency, can you please explain why users of the binaries you guys provide were unaffected by the bug which just got fixed in the official code repository on https://github.com/phenixcoin/Phenixcoin ? Apparently the issue only occured for linux users who compiled their own binaries from the public source, and noticeably so because the wallet sync got completely stuck. I cannot imagine a setting or environment where the former code wouldn't cause this behavior. Are you compiling the binaries you release on phenixcoin.com from a separate codebase which differs from the repo on github, and if so, why? Thanks I was kind of wondering the same thing as well, I delete my block chain and it downloaded fine.. its not a different code base. Most people where not effected because they already had the block chain and it was stalling on a block with a diff change. trust me, I will be looking into why the windows binary worked.. its pretty easy to setup a mingw compile env for windows, grab the code for 6.4.5 and try it.. we have full transparency with the coin.. Thanks, sounds reasonable, in particular that most people probably already had the complete blockchain with the latest retarget block in their wallets. Must be some really weird windows side effect then. Ya but I still want to know why.. Yeah
|
|
|
|
weav
Sr. Member
Offline
Activity: 350
Merit: 250
- "Bitcore (BTX) - Airdrops every Monday"
|
|
June 20, 2013, 02:13:32 AM Last edit: June 20, 2013, 02:24:51 AM by weav |
|
Another bug, mentioned earlier, still occurs: after running the wallet for a while (hours) the "Synchronizing with network.." progress bar reappears saying: 327431 blocks remaining and when hovering over it with the mouse: Downloaded block 46579 of 374010 although there are only 46579 blocks in total by now. Errors like the following show up in the -printtoconsole log: ERROR: FetchInputs() : 7f86e710b0 mempool Tx prev not found 73a5af9661 stored orphan tx 7f86e710b0 (mapsz 15) ERROR: FetchInputs() : d02d4ba85b mempool Tx prev not found 8ca4687af1 stored orphan tx d02d4ba85b (mapsz 16) received getdata for: tx de72b672826e9013aa7f ResendWalletTransactions() ERROR: FetchInputs() : 38b44facd9 mempool Tx prev not found c39f7dc03d stored orphan tx 38b44facd9 (mapsz 17)
|
|
|
|
nearmiss
|
|
June 20, 2013, 02:16:55 AM |
|
not to spam, but brand new pool up: http://pxc.scryptmining.com* stratum-only * proportional payouts per block (no pplns warmup!) * variable diff per worker (lots of hashpower? reduce your bandwidth. low hashpower? Don't get stung by a high static pool-wide diff!) Come check us out
|
Profit-Switching Pool w/ Vardiff -> http://hashco.ws Optionally keep the alts we mine or auto-trade for BTC. In addition can be paid out in any of: 365, AC, BC, BTC, C2, CINNI, COMM, FAC, HBN, MINT, PMC, QRK, RDD, WC, XBC
|
|
|
MaGNeT
Legendary
Offline
Activity: 1526
Merit: 1002
Waves | 3PHMaGNeTJfqFfD4xuctgKdoxLX188QM8na
|
|
June 20, 2013, 06:02:15 AM |
|
Another bug, mentioned earlier, still occurs: after running the wallet for a while (hours) the "Synchronizing with network.." progress bar reappears saying: 327431 blocks remaining and when hovering over it with the mouse: Downloaded block 46579 of 374010 although there are only 46579 blocks in total by now. Errors like the following show up in the -printtoconsole log: ERROR: FetchInputs() : 7f86e710b0 mempool Tx prev not found 73a5af9661 stored orphan tx 7f86e710b0 (mapsz 15) ERROR: FetchInputs() : d02d4ba85b mempool Tx prev not found 8ca4687af1 stored orphan tx d02d4ba85b (mapsz 16) received getdata for: tx de72b672826e9013aa7f ResendWalletTransactions() ERROR: FetchInputs() : 38b44facd9 mempool Tx prev not found c39f7dc03d stored orphan tx 38b44facd9 (mapsz 17) Not really a bug, just one or more people who are trying to get us on the LTC (or another) chain. Just ignore it
|
|
|
|
weav
Sr. Member
Offline
Activity: 350
Merit: 250
- "Bitcore (BTX) - Airdrops every Monday"
|
|
June 20, 2013, 09:03:31 AM |
|
Another bug, mentioned earlier, still occurs: after running the wallet for a while (hours) the "Synchronizing with network.." progress bar reappears saying: 327431 blocks remaining and when hovering over it with the mouse: Downloaded block 46579 of 374010 although there are only 46579 blocks in total by now. Errors like the following show up in the -printtoconsole log: ERROR: FetchInputs() : 7f86e710b0 mempool Tx prev not found 73a5af9661 stored orphan tx 7f86e710b0 (mapsz 15) ERROR: FetchInputs() : d02d4ba85b mempool Tx prev not found 8ca4687af1 stored orphan tx d02d4ba85b (mapsz 16) received getdata for: tx de72b672826e9013aa7f ResendWalletTransactions() ERROR: FetchInputs() : 38b44facd9 mempool Tx prev not found c39f7dc03d stored orphan tx 38b44facd9 (mapsz 17) Not really a bug, just one or more people who are trying to get us on the LTC (or another) chain. Just ignore it Oh Weird. How do they do it?
|
|
|
|
HuuHachu
|
|
June 20, 2013, 09:16:44 AM |
|
Another bug, mentioned earlier, still occurs: after running the wallet for a while (hours) the "Synchronizing with network.." progress bar reappears saying: 327431 blocks remaining and when hovering over it with the mouse: Downloaded block 46579 of 374010 although there are only 46579 blocks in total by now. Errors like the following show up in the -printtoconsole log: ERROR: FetchInputs() : 7f86e710b0 mempool Tx prev not found 73a5af9661 stored orphan tx 7f86e710b0 (mapsz 15) ERROR: FetchInputs() : d02d4ba85b mempool Tx prev not found 8ca4687af1 stored orphan tx d02d4ba85b (mapsz 16) received getdata for: tx de72b672826e9013aa7f ResendWalletTransactions() ERROR: FetchInputs() : 38b44facd9 mempool Tx prev not found c39f7dc03d stored orphan tx 38b44facd9 (mapsz 17) Not really a bug, just one or more people who are trying to get us on the LTC (or another) chain. Just ignore it Oh Weird. How do they do it? Not sure *how* they do it ... probably a misconfigured port somewhere. But normally this should not happen because litecoin clients should not be allowed to talk to phenixcoin clients. Each coin should use a different identifier (often called "magic number"), but pxc and most other coins did not change this identifier when copying the code base of litecoin (this identifier is 4 bytes, in the pchMessageStart variable) With a correct setting of this variable to something else (as long as it is not used by another coin), it would take at least someone manually copying the litecoin blockchain into pxc directory to have this problem.
|
noble: 9mKQpsfLeabjFsPv3YR9zYoAVymDPyfjCp
|
|
|
JohnCar (OP)
|
|
June 20, 2013, 12:20:45 PM |
|
Morning bump...
|
TIT coming soon..............
|
|
|
maxpower
|
|
June 20, 2013, 04:11:18 PM |
|
I updated my Mac build of the PhenixCoin wallet to version 0.6.4.7, which resolved a syncing problem for me. The URL is at the Mac Wallets thread listed in my signature. Enjoy!
|
|
|
|
MaGNeT
Legendary
Offline
Activity: 1526
Merit: 1002
Waves | 3PHMaGNeTJfqFfD4xuctgKdoxLX188QM8na
|
|
June 20, 2013, 04:15:30 PM |
|
I updated my Mac build of the PhenixCoin wallet to version 0.6.4.7, which resolved a syncing problem for me. The URL is at the Mac Wallets thread listed in my signature. Enjoy!
Great! Thanks!
|
|
|
|
Taxidermista
Legendary
Offline
Activity: 1147
Merit: 1001
|
|
June 20, 2013, 05:33:08 PM |
|
Hello all just wanted to let everyone know there is a new client for PhenixCoin ** PLEASE UPDATE YOUR CLIENTS ** - Version 6.4.7 is now available, please download it before block 46500. You can download the client from here http://phenixcoin.comChanges that have been implemented are: Difficultly changes every 480 blocks max change is 80%. We have also added checkpoints as well. Please help spread the word of the new client for PhenixCoin. Thank you for your support and happy mining! Thanks John I don't know if this explorer is working properly: http://explorer.phenixcoin.com/chain/PhenixcoinBut the difficulty changes every 300 blocks, not 480.
|
|
|
|
weav
Sr. Member
Offline
Activity: 350
Merit: 250
- "Bitcore (BTX) - Airdrops every Monday"
|
|
June 20, 2013, 07:00:55 PM Last edit: June 20, 2013, 09:28:01 PM by weav |
|
Hello all just wanted to let everyone know there is a new client for PhenixCoin ** PLEASE UPDATE YOUR CLIENTS ** - Version 6.4.7 is now available, please download it before block 46500. You can download the client from here http://phenixcoin.comChanges that have been implemented are: Difficultly changes every 480 blocks max change is 80%. We have also added checkpoints as well. Please help spread the word of the new client for PhenixCoin. Thank you for your support and happy mining! Thanks John I don't know if this explorer is working properly: http://explorer.phenixcoin.com/chain/PhenixcoinBut the difficulty changes every 300 blocks, not 480. It changes every 600 blocks, see https://bitcointalk.org/index.php?topic=237329.msg2524705#msg2524705This takes ideally 15 hours (but can take much longer or less, depending on changes in the network hashrate)
|
|
|
|
Taxidermista
Legendary
Offline
Activity: 1147
Merit: 1001
|
|
June 20, 2013, 07:01:58 PM |
|
Hello all just wanted to let everyone know there is a new client for PhenixCoin ** PLEASE UPDATE YOUR CLIENTS ** - Version 6.4.7 is now available, please download it before block 46500. You can download the client from here http://phenixcoin.comChanges that have been implemented are: Difficultly changes every 480 blocks max change is 80%. We have also added checkpoints as well. Please help spread the word of the new client for PhenixCoin. Thank you for your support and happy mining! Thanks John Now is 600??? I don't think so. I don't know if this explorer is working properly: http://explorer.phenixcoin.com/chain/PhenixcoinBut the difficulty changes every 300 blocks, not 480. It changes every 600 blocks, see https://bitcointalk.org/index.php?topic=237329.msg2524705#msg2524705This takes ideally 15 hours (but can take much longer or less)
|
|
|
|
weav
Sr. Member
Offline
Activity: 350
Merit: 250
- "Bitcore (BTX) - Airdrops every Monday"
|
|
June 20, 2013, 07:57:56 PM |
|
Another bug, mentioned earlier, still occurs: after running the wallet for a while (hours) the "Synchronizing with network.." progress bar reappears saying: 327431 blocks remaining and when hovering over it with the mouse: Downloaded block 46579 of 374010 although there are only 46579 blocks in total by now. Errors like the following show up in the -printtoconsole log: ERROR: FetchInputs() : 7f86e710b0 mempool Tx prev not found 73a5af9661 stored orphan tx 7f86e710b0 (mapsz 15) ERROR: FetchInputs() : d02d4ba85b mempool Tx prev not found 8ca4687af1 stored orphan tx d02d4ba85b (mapsz 16) received getdata for: tx de72b672826e9013aa7f ResendWalletTransactions() ERROR: FetchInputs() : 38b44facd9 mempool Tx prev not found c39f7dc03d stored orphan tx 38b44facd9 (mapsz 17) Not really a bug, just one or more people who are trying to get us on the LTC (or another) chain. Just ignore it Oh Weird. How do they do it? Not sure *how* they do it ... probably a misconfigured port somewhere. But normally this should not happen because litecoin clients should not be allowed to talk to phenixcoin clients. Each coin should use a different identifier (often called "magic number"), but pxc and most other coins did not change this identifier when copying the code base of litecoin (this identifier is 4 bytes, in the pchMessageStart variable) With a correct setting of this variable to something else (as long as it is not used by another coin), it would take at least someone manually copying the litecoin blockchain into pxc directory to have this problem. Thanks, that's odd indeed, I mean what are the odds for that working? Shouldn't the proof of work system reject locally invalid blocks from a different chain and prevent this? Well, they managed to trick my client somehow
|
|
|
|
erundook
|
|
June 20, 2013, 08:32:48 PM |
|
I updated my Mac build of the PhenixCoin wallet to version 0.6.4.7, which resolved a syncing problem for me. The URL is at the Mac Wallets thread listed in my signature. Enjoy!
there is also a free online wallet at my sig which started supporting PXC today
|
|
|
|
nawazish1
Sr. Member
Offline
Activity: 462
Merit: 250
PXC Research Team
|
|
June 20, 2013, 08:49:31 PM |
|
I updated my Mac build of the PhenixCoin wallet to version 0.6.4.7, which resolved a syncing problem for me. The URL is at the Mac Wallets thread listed in my signature. Enjoy!
there is also a free online wallet at my sig which started supporting PXC today I was really waiting for you to do this. Now more people can come to PXC easily.
|
PXC: PmfFgdwwcXPa1QUmtVJevdPfHhmhztHHCv BTC: 1P22tVABsd85L7kkpTmohCv5vK2BypFz3H Phoenixcoin (PXC), a decentralised open source digital currency.
|
|
|
mika1977
|
|
June 21, 2013, 02:59:18 AM |
|
I updated my Mac build of the PhenixCoin wallet to version 0.6.4.7, which resolved a syncing problem for me. The URL is at the Mac Wallets thread listed in my signature. Enjoy!
there is also a free online wallet at my sig which started supporting PXC today What is the operating principle of the online wallet?
|
|
|
|
erundook
|
|
June 21, 2013, 01:03:58 PM |
|
I updated my Mac build of the PhenixCoin wallet to version 0.6.4.7, which resolved a syncing problem for me. The URL is at the Mac Wallets thread listed in my signature. Enjoy!
there is also a free online wallet at my sig which started supporting PXC today What is the operating principle of the online wallet? for people to have a portion of their coins for easy online access.
|
|
|
|
B. Tazed
Newbie
Offline
Activity: 28
Merit: 0
|
|
June 28, 2013, 05:37:42 PM |
|
Nice to have devs on top of things.
|
|
|
|
B. Tazed
Newbie
Offline
Activity: 28
Merit: 0
|
|
June 28, 2013, 05:42:16 PM |
|
Nice to have devs on top of things.
6.4.8 available.
|
|
|
|
lucerohein
Newbie
Offline
Activity: 56
Merit: 0
|
|
July 04, 2013, 09:52:31 PM |
|
Updated, any newer updates on the way?
|
|
|
|
MaGNeT
Legendary
Offline
Activity: 1526
Merit: 1002
Waves | 3PHMaGNeTJfqFfD4xuctgKdoxLX188QM8na
|
|
July 23, 2013, 02:50:05 PM |
|
Update on Feathercoin forum: https://forum.feathercoin.com/index.php?topic=2939.msg22770#msg22770
Team,
Unfortunately, just when you think a piece of software is ready to rock and roll, a last minute bug or two appears and slaps you in the face. Since UNOCS Bridge deals with the secure transfer of coins between parties, I understand the dev team to spend additional time stomping it out. Obviously, this launch didn't go as expected.. ok, lessons learned. I accept responsibility and will just have to hope that the end result will justify the pain up-front in your eyes.
I'm just waiting for the final green light from the team. As soon as I hear back, I'll immediately update this post.
John justabitoftime Update on http://UNOCS.com now too Notice - Killing bugs is taking longer then I thought. I am working hard to get this done asap. I am hoping to be able to open the site in a couple more hours. ~iamatrix
|
|
|
|
|