B&C Exchange 5.0.1 release - upgrade before 18 July!

B&C Exchange
#31

Run bcexchanged getinfo. If it returns "version" : "v5.0.1-beta" then you’re minting with the 5.0.1 client and fully supports the upcoming protocol.

If you want to know whether you’re voting for the 5.0 protocol (to make sure the bug is fixed for example) you can find a block you minted by looking for the last “new block found” in debug.log. It’s followed by a line giving the hash of the block you found. Then you can run bcexchanged getblock <the hash> and in the vote section it should show "versionvote" : "5.0".

2 Likes
#32

Still no version release updates to the website, main thread or Twitter account. How do we take these over so we can update them? @CoinGame @tomjoad Do we need to talk to this Angela? Who controls these accounts and how do shareholders update things?

#33

Do we need to pass a motion of hand over the dev fund, website, twitter account to reputed signers?

1 Like
#34

I’m not sure about the social media accounts. I may have access to them but I’d have to do some digging. The website itself is open source and anyone can submit a pull request to update it. https://github.com/BC-Exchange/bcexchange.org

3 Likes
#35

{
“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.

#36

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”
}
}

1 Like
#37

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.

3 Likes
#38

{
“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. :slight_smile:

#39

Less than 6 hours to mint for ‘any user’ below 5.0 :sunglasses:

1 Like
#40

@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”

#41

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

1 Like
#42

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.

@JetJet13, @Ben, @CoinGame

#43

@Mark, thanks for the heads up. B&C Explorer daemon has been updated.

Cheers.

1 Like
#44

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”
}
}

#45

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.

#46

almost the same

#47

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.

1 Like
#48
#49

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?

#50

Where does it indicate that?