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.