{
“2.0” : {
“blocks” : 75,
“block_percentage” : 3.75,
“switch_to_date_time” : “”
},
“4.0” : {
“blocks” : 275,
“block_percentage” : 13.75,
“switch_to_date_time” : “2016-08-01 14:00:00 UTC”
},
“5.0” : {
“blocks” : 1650,
“block_percentage” : 82.5,
“switch_to_date_time” : “2016-07-18 14:00:00 UTC”
}
}
what does this mean?v4.0.1 forked ?@sigmike
Recently, number of connection always = 5.
There are no apathetic miners for B&C, LOL
{
“2.0” : {
“blocks” : 15,
“block_percentage” : 0.75,
“switch_to_date_time” : “”
},
“4.0” : {
“blocks” : 283,
“block_percentage” : 14.15,
“switch_to_date_time” : “2016-08-01 14:00:00 UTC”
},
“5.0” : {
“blocks” : 1702,
“block_percentage” : 85.1,
“switch_to_date_time” : “2016-07-18 14:00:00 UTC”
}
}
It means the protocol “4.0 or more” reached 90%, so a switch to 4.0 would happen on August 1st. But it won’t. It’s an unusual case that was not anticipated in the RPC command.
What will happen is that the protocol will switch to 5.0 today, and then it won’t check anything about 4.0 anymore (because we will already be beyond). The RPC will probably continue to report the 4.0 switch time though.
Any user running a version below 5.0 will start to reject blocks created by 5.0 after 14:00 UTC today. If they mint they will run on an isolated chain and end up banned.
{
“4.0” : {
“blocks” : 278,
“block_percentage” : 13.9,
“switch_to_date_time” : “2016-08-01 14:00:00 UTC”
},
“5.0” : {
“blocks” : 1722,
“block_percentage” : 86.1,
“switch_to_date_time” : “2016-07-18 14:00:00 UTC”
}
}
V2.0 disappears in these 2 days, I guess some mines are not apathetic, but lazy. 
Less than 6 hours to mint for ‘any user’ below 5.0 
@sigmike, is there something wrong
{
“4.0” : {
“blocks” : 242,
“block_percentage” : 12.1,
“switch_to_date_time” : “2016-08-01 14:00:00 UTC”
},
“5.0” : {
“blocks” : 1758,
“block_percentage” : 87.9,
“switch_to_date_time” : “2016-07-19 14:00:00 UTC”
}
}
“switch_to_date_time” has moved 1 day ahead but my client reports “protocolversion” : “5.0”
No it’s a problem with the RPC command only. It doesn’t take into account the fact the protocol has already switched. I created an issue for these 2 problems: https://bitbucket.org/JordanLeePeershares/bcexchange/issues/41/fix-getprotocolvotes-switch-dates
Please, upgrade B&C Explorer daemon.
I see it as /Siglee:4.0.0/B&C Exchange:4.0.0(v4.0.1-beta)/ in connected nodes to my client.
Explorer shows:
Protocol Version 2.0
Is it correct?
BTW, congratulation 100% V5.0 protocol.
{
“5.0” : {
“blocks” : 2000,
“block_percentage” : 100.0,
“switch_to_date_time” : “2016-07-20 14:00:00 UTC”
}
}
after hard fork and no newer version than 5.0 there’s no way for it not to be 100%. what’s more important is current difficulty compared to before.
almost the same
Is it ok to unsticky this now?
Edit: I just did this. Let me know if it should still be stickied. It seems that the protocol successfully switched, so there’s no more need for the thread.
I am installing v 5.0.1 and the client indicate v 2.0 at the beginning of the blockchain download.
Is this normal?
The current version should be v 5.0 on the long run and also right from the start?
Where does it indicate that?
At least in the software details thumbnail.
I am out of the office now.
I ll let u know tomorrow.
Solved by waiting a bit.
Hey guys,
The block explorer daemon has not processed blocks past 551,626. I upgraded the daemon on July 19 (1 day after the deadline) and it was going fine until July 26.
Has anyone else come across this before ? I believe the solution would require a re-download of the blockchain. Let me know.
Cheers.
I noticed it and started a thread
but the problem was only solved for the Rasp-Pi.