A defect in B&C Exchange version 4.0.0 has been discovered that will require B&C minters to upgrade to 4.0.1 before the protocol switch date, which will be two weeks after 90% of blocks are minted with 4.0.0 or 4.0.1. Currently, only 21.9% of blocks have a vote for protocol 4.
Version 4.0.1 also has a new RPC called getprotocolvotes that produces the following output:
This RPC will tell us exactly when the switch time will be after protocol 4 votes exceed 90%. It was developed solely by Eleven, who just joined us as a developer. Congratulations to @Eleven for getting your first code to the production environment! That was quick!
Finally, it is important everyone make the effort to upgrade. A delay in achieving a 90% vote for the new protocol will produce the same delay in the network’s ability to use the reputation system to vote for and reward reputed signers. Let’s move quickly.
Yes. Protocol switch date is not set until we reach 90%. So getting the message out there that Minter’s upgrade is important. Thanks to the getprotocolvotes RPC it’ll be easier to track which way the vote trend is going.
well that sucks, I just upgraded my Pi2 last week to 4.0.0 and now I’m going away for 3 weeks so I won’t be able to upgrade until I am back. What’s the defect? Should I shut down the Pi because that’s all I could do for now?
Have all buyers been contacted on Bitmessage about the upgrade? I’m not sure if people are still monitoring that, but it might help. They need to be told to regularly monitor the thread and this forum for client updates.
Isn’t it possible to broadcast the upgrade notification through the BCE client?
I mean, everybody who’s minting has it running.
With e.g. a headless RaPi and no GUI, they find it in the errors section of the getinfo RPC, which they should check from time to time (because of block height etc.).