This article was first published on The Blueprint by Bluzelle - Medium
It is now the end of November and the Bernoulli release is starting to really shine! I hope everyone has had a terrific November and had a chance to try out the interim new version of our testnet that was released in November.
As I write this update, we are a month away from the release of Bluzelle’s Bernoulli release. The Bluzelle team is pushing hard on the key deliverables for Bernoulli, as you have been hearing in past updates in the 2nd half of 2018. Our two new October additions (Matthew and Paul) to the team are well-integrated and firing on all cylinders to deliver a quality product.
To continue with a new tradition I started in October, this section will share with the community specific and interesting developments, quirks, challenges, bug fixes, last-minute feature additions, and new learnings that happened during the previous month of development. We want to engage the community to know the story behind the development of the product and the team building it.
- We have completely redesigned the client wire protocol and architecture to consider PBFT and permissioning. Now, everything is completely powered by protobuf.
- We have created explicit database management APIs in order to allow the attachment of metadata. This gives Bluzelle another one of the key features of a real database.
- Our client documentation has been beefed up considerably. Check it out at: https://devel-docs.bluzelle.com/client-development-guide/v/v0.4.x/client-architecture
Bernoulli Release Progress
Bernoulli is moving along quickly towards our goal of an end-of-2018 delivery. As you know, the two key deliverables for Bernoulli are PBFT consensus and permissioning.
We have completed all the individual pieces necessary for a PBFT consensus engine and are deeply engaged in the integration of these pieces and the testing of the PBFT engine as a whole. PBFT ...
To keep reading, please go to the original article at:
The Blueprint by Bluzelle - Medium