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.