Topic: **MANDATORY UPGRADE REQUIRED** [ANN] B&C Exchange - All users must upgrade - page 2. (Read 174430 times)

How or where can i purchase BKS?

I want to purchase 204 BlockShares. I'll pay $6.50 per share. If anyone is interested, please PM me.

At the request of sigmike I would like to make a modification to the B&C 5.0 specifications, which are described in the original post.

There has been discussion around adding the capability to abstain from voting when minting for a long time, going back to at least December 2014 when woodstockmerkle wrote about the possibility.

I have been wary of any solution that would require shareholders to actively and specifically vote no on a grant or motion to prevent its passage. There is, however, a limited manner in which abstentions can be employed without creating a situation where "no" voting is a necessity. Rather than set default data feed providers, I am persuaded that simply setting the default voting behavior on a new install to abstain is the best course of action to address the noise that comes from apathetic voting. We can do this with a simple check box labeled "Abstain" located to the right of the voting buttons on the Voting tab.

Blocks found by abstaining minters simply won't count when deciding whether a motion or grant has passed. Consider a scenario where 50% of blocks in a 10,000 block series have an abstention. This would mean that only 2501 blocks need to have a vote for a particular grant in order for it to pass.

We will still be including a new drop down list of data feed providers, so they will be much easier to select and configure than they are now. We just won't automatically set a default.

Other than these changes, the 5.0 release is now code complete. Hopefully the team will be able to make the changes quickly and we can release very soon.

Is it a working exchange now or still under development?

We are discussing best ways of speeding up the release of a MacOSX client. We appreciate everyone's patience.

In thinking about how to set up an election for default data providers, I start from the point that what we need in the client is a list of data feed providers, along with URLs, signature URLs, address and the percentage of the votes the provider received.

To derive the percentage of votes for each provider I suggest that all data feed providers submit a motion that represents their candidacy to be a default data provider. It might say something like this:

Voting for this motion will increase the probability that provider A will be chosen as a default data feed provider upon a specific installation of B&C Exchange version 5. This represents the candidacy of provider A to become a default data feed provider.

While data feed providers will likely want to say why shareholders should vote for them, that shouldn't be a part of the motion in my opinion.

The date at which votes should begin to be counted will be April 25th UTC. This means @Cybnate, @Cryptog, @crypto_coiner and any other candidate will need to post their motion well in advance of that so it can be added to clients and data feeds. And yes, of course each data feed provider will vote for itself and no other. That works to accurately reflect the real popularity of each feed. Voting will end when the 5.0 release is otherwise code complete. A minimum of 5000 blocks and a maximum of 20000 blocks of votes will be counted, starting on April 25th. Individual shareholders may vote for none, one, some or all of the competing default data feed motions.

A hypothetical example will clarify how votes are to be counted:

The release is code complete except for the default data feed voting results 12,000 blocks after the start of April 25th. Within those 12,000 blocks, provider A received 6000 votes while provider B received 4000 votes for their respective motions. This means that 60% of the time running through the client install, provider A will be selected as the default data feed provider while the other 40% of the time provider B would be selected initially by default.

Any data feed provider who receives even a single vote will be included in the 5.0 release as a default data provider.

For any release that occurs more than 90 days from the release of 5.0, a new vote will be held for default data feed providers.

Release the Mac OSX version ASAP, please.

We have updated our thread title to capture the attention of users.

All shareholders are reminded that they must upgrade to version 4.0 immediately. The protocol switch date will be two weeks after 90% of blocks are minted with 4.0.0 or 4.0.1.

Visit bcexchange.org to download 4.0.1 for Windows and Linux or use the links below. Mac OSX builds will arrive in the near future.

Windows: https://bitbucket.org/JordanLeePeershares/bcexchange/downloads/bcexchange-4.0.1-win-gitian.zip

Linux: https://bitbucket.org/JordanLeePeershares/bcexchange/downloads/bcexchange-4.0.1-linux-gitian.zip