Yes, the one with the hardfork but there's a new fix for the blockchain stuck and some checkpoint but the new wallet for that is not yet released.
Will that wallet be released before or after the hardfork?
It doesn't have to because it only adds checkpoints of historic blocks. When you are not downloading the entire chain, you don't need it. But for the guys setting up extra nodes to support the network, it makes life a bit easier.
But the code is already released and everyone is free to compile it for Windows if they want
For the hard fork, current version 1.0.1 is enought.
The latest version, however, adds more than just checkpoints. There is 2 other changes:
1) After this, the wallet won't even try to download blocks from old nodes. I think it is safe
now to add this, there is enought nodes with protocol version 60017. It will block out problems
caused by old nodes still alive pushing wrong blocks.
https://github.com/MsCollec/sync/commit/7b8a9864c7ef473f31b075c23c29fc8c7c247d662) When I changed the minimum stake difficulty to speed up the blockchain, I missed one point which needed also a modification. It made blockchain stuck at 8200 a bit worse. My fault, but now fixed. The blockchian will still stuck at 8200, but now it will recover when the first new block is found.
https://github.com/MsCollec/sync/commit/e7fca001fd184936ed29b20d4a9d87a6857fa268No need to update from 1,0,1 to 1,0,2, if you are on the top of the blockchain. But if you are experiencing syncing problems, this should help.
can you also advise please; previously, when staking has hit an orphan block - my wallet has gone OOS and does not recover until I delete the entire blockchain and resync.
i am not sure if this has been made clear yet, is this issue now fixed?
I having been staking good blocks, i've not staked any orphan blocks since the last time this occurred but an affirmation that this issue is now corrected would be very much appreciated.
thanks.
This happened to me as well, because my wallet started following a fork when internet connection here on Cyprus was intermittent.
The only way to avoid this is to avoid bad nodes, which I think point 1 is an attempt of.
If the coins start staking on a fork, that's not really relevant to our chain and they will not be able to stake "for real" until you connect to the correct chain.
No, AFAIK, this is not fixed, unless it is a side effect of the problems fixed. I'll put this on the list, and please send me PM if you encounter this with the 1.0.2 version or later.
I'm going to be honest: If this probelms is still there, we might have similar problems after the fork and a some, maybe a lot of you will suffer from this.
I'm trying to figure out what will happen at the fork transition; this might be speculation, but this is how I think it will go (please comment, if you disagree or notice something I did not):
1. the weight paraneters is 1000 times bigger after fork; that means the blockrate will be 1000 times more frequent, until retarget adjusts it. If there is now 6 blocks/hour, the speed will be 6000 blocks/hour, ie a couple of blocks per second. Not sure how long this will stay, it can actually adjust it to preset 1/min within a few minutes.
2. If this lasts long enought, *every* coin online will get stake.. and after that it takes 6 hours to get next.. but I think this won't be the case, adjust will likely be faster. However, just to be sure, it might be good if not everyone is online at the transition time. It's up to you to decide if you want to keep your wallet online.
But there will also be orhpans.. and if there is such problem, we almost certainly will see it when the rate is 2 blocks/second :-(. If this happens to you, I just hope you'll be patient and prepare for it. You''ll anyway get your stake when you get your chain up to date. And you have an option to stay offline at the transition time and start your wallet at will. (if you are interested, I'll keep my online :-)
But before that, I'll do my best to find if this still is a problem. Unfortunately at this timeline and no possibility to test it, most likely I won't find it.
If you all want, we have an option to postpone the fork. My opinion is not to postpone it (there is no reason to assume anything unfixable ḧappens)
Edit: sorry if this is just feeding a troll. If there is no problms with orphan blocks, then the fork is also safe