Thanks, it would be good to compile a list of data feed providers to make it easier for people to decide

Peershares such as NuBits and B&C Exchange are the most advanced form of decentralised blockchain governance to date. The work I have already done establishes me as the leading innovator in decentralised blockchain governance.

Hi guys, I am Xiaochuan Wu. I prefer you call me Eleven. Thank you very much ,Jordan. Thank you everyone here. I am very pleased to join B&C Exchange development team. B&C Exchange development team is doing cool and awesome things. I believe It would have a good future. I would do my best to make it better and better. Now I am together with B&C Exchange family.
Cheers.

We have a new release candidate for B&C Exchange 4.0 that will enter testing tomorrow:

https://bitbucket.org/JordanLeePeershares/bcexchange/downloads/bcexchange-4.0.0-RC2-win-gitian.zip
https://bitbucket.org/JordanLeePeershares/bcexchange/downloads/bcexchange-4.0.0-RC2-linux-gitian.zip

4.0 will allow shareholders to vote for signers and allows signers to prepare for trading operations in the following production release.

CoinGame will keep us informed in the coming days regarding what he finds while testing.

NuBits and B&C Exchange share the same team. This gives B&C the advantage of having people work on it that have worked with the code base for a year or two in most cases. It has the disadvantage of meaning that when the team is focused on NuBit development, B&C Exchange development necessarily gets less attention and work.

The NuBit 2.1 release has been a major undertaking. We thought we were nearly done with it a month ago, but testing revealed some important performance issues that were difficult and time consuming to track down and remedy. The NuBits 2.1 release is very close to being ready for beta release. As a result, the team is once again turning its focus to B&C Exchange. The B&C Exchange 4.0 release will receive additional testing in the coming days. Over the course of the last month, glv has continued to make progress on developing the exchange messages (to be released after 4.0).

Sigmike and I are discussing a couple ways we could bring additional developers to the project to speed implementation. While I regard the pace of development as a disappointment to date, we have effectively conserved our funding and I am more convinced that B&C Exchange has a viable design than I was six months ago. Progress has taken longer than expected due to lower availability of developers than was expected, but the project is still very viable and is in fact moving forward.

While reading the white paper a doubt emerged about market makers / liquidity providers:

(Inside B&C Exchange protocol/structure) Are ONLY core clients (that download the FULL blockchain) gonna be supported for liquidity providers?

OR

Are Simplified Payment Verification Clients (e.g. Electrum) gonna be supported too?

B&C Exchange client version 4.0 is now code complete, although that code has not yet been merged into the master branch of the BCExchange repository which masterOfDisaster was observing. We will begin testing shortly. Version 4.0  includes complete implementations of all voting features needed for the exchange and a fully functional reputation voting system. That is major progress. I estimate we are 35% code complete at this point.

sigmike has spent the last month on Nu version 2.1, which is also now code complete and partially tested. So there are no contributions from sigmike in the last month on B&C Exchange. I have mentioned in posts in the past about how the Nu and B&C team are shared resources. He is just turning his attention to B&C Exchange again, now that Nu 2.1 is code complete.

About a month ago I began recruiting an additional developer for B&C Exchange. Obviously, such a vacancy means progress is not occurring at the optimal speed. However, it also implies the pace will increase once the position is filled. That position was recently filled by glv, and he has just completed his first successful set of tasks, or pull request.

So, most of the progress that has been made was understandably overlooked by masterOfDisaster. Additionally, today we have glv and sigmike focusing on B&C Exchange where over most of the last month they weren't working on it because glv just joined the project days ago and sigmike was working on Nu 2.1.

What do I overlook?

https://bitbucket.org/JordanLeePeershares/bcexchange/pull-requests/ contains exactly one pull request in the last 5 weeks - and that one is still open.

I'm happy to be able to announce that glv (glv2 on GitHub) has joined the B&C Exchange development team. He has done excellent work in the Peercoin

It looks like version 4.0.0 is being worked on.
More details here: https://bitbucket.org/JordanLeePeershares/bcexchange/branch/4.0-stable#diff

I fully second your assessment about BCE offering a wallet service. I've written my take on this at another place (https://discuss.nubits.com/t/passed-motion-to-provide-seed-funding-for-b-c-exchange-a-decentralized-exchange-built-on-the-peershares-platform/2001/539):

For the wallet service there's a charge: all transactions that utilize the BCE network as a wallet service require transactions; they have a size and cost BKC

If additional funding is received, we could see additional goodies such as an Android interface that simultaneously functions as a wallet for assets being traded.

If you requested and paid for BKS via email and did not receive our bulk email requesting BKS addresses, there is no need to wait for us to contact you individually. You can just take the initiative to send us your BKS address(es) by email at bkssale@vistomail.com, using the same email address you used to pay for your BKS.