I wanted to clarify that we ought to raise the difficulty above the floor of 0.00024414. When we do that, clients that haven’t upgraded will work fine. So throw all the minting power you can at the network right now please.
The network is now finding more than one block per minute and difficulty has bottomed out at 0.00022890 and is on its way up.
The block explorer is running behind right now. We’re working with the developer to get it updated to 0.5.1 and resynchronized ASAP.
We apologize for the inconvenience.
All my NSR is minting now.
When will 0.5.1 available?
Clients not upgraded will begin working again when the difficulty rises above 0.00024414, which is likely to occur in less than 24 hours. Be warned that if you don’t upgrade you will once again be isolated from the network when the difficulty drops below 0.00024414, which is almost certain to happen at some later date.
I suggest to split the download package into 32 bits and 64 bits two groups. Most of us just want to get one version. Thanks.
it seems that I never had to upgrade 2 times in a row within a few days with peercoin-qt.
is nubits blockchain experiencing some issue right now?
Is it possible to provide the ARM daemon?
The 0.5.0 mandatory upgrade had been planned for over a month. There was nothing hurried or urgent about it. We had identified over a month ago that there was a minor protocol flaw that prevents the difficulty from dropping below 0.00024414. It was intended that the 0.5.0 release would remove this flaw. And it did, except when a blockchain reorganization occurs. In that case the floor was still being mistakenly imposed in the 0.5.0 version. The difficulty did indeed recently drop below 0.00024414. 0.5.0 clients then became unable to perform reorganizations, causing multiple forks throughout the network. The solution to achieving consensus was to remove two lines of code that separately enforced the difficulty floor in the case of a reorganization. The removal of these two lines enforcing the difficulty floor is the only difference between 0.5.0 and 0.5.1.
In summary, the portion of the network using 0.5.1 is functioning optimally and is producing more than 1 block per minute. If you are using an older version, chances are high you have forked from the longest, consensus chain. The 0.5.0 client will accept the longest chain and its immediate problems will be resolved when the difficulty rises above 0.00024414 again, which I expect to happen in less than 24 hours. However, it is still important that you upgrade to 0.5.1. If you don’t, you will be separated from the network the next time difficulty falls below 0.00024414, which is almost certain to happen at some point in the future.
Exactly that!
@CoinGame the world needs you! The world needs your ARMv6 binaries for RaspberyPi! 
1 Like
ok. tks for clarifying.
working on it.
The difficulty is currently 0.00024587, just above the old floor of 0.00024414. As expected, all 0.5.0 clients joined the 0.5.1 clients as we crossed that threshold. Everyone using either 0.5.0 or 0.5.1 is now on the same chain. I expect that to continue as long as the difficulty is above 0.00024414. So, you still need to upgrade to 0.5.1 if you have not already done so, because the difficulty is likely to fall below 0.00024414 at some point in the future.
plplplplpleeaaaaase! 
…I can’t believe I’m the only one who is desperately waiting for ARM binaries - am I?
1 Like
Ah crap sorry I built it and forgot to share the link
https://drive.google.com/file/d/0B96pmq-lU9NQQWh4Z1poZHJhelE/view?usp=sharing
That’s the 5.1 ARM daemon
3 Likes
Yeah! Thank you!
+/u/nbtip CoinGame beer
…I knew it wouldn’t work…
Thanks!
This topic is no longer a banner. It will no longer appear at the top of every page.