Welcome to my end-of-August update on the development of the Bluzelle DB. With the Lovelace testnet now having been public for two full months, it is exciting to start to see projects arise, that are using the database. Despite the database being in testnet, it has in fact been running for over 1.5 months, as of the date of this blog. This is a good testement to the stability of the nodes, despite the testnet being completely open for use by the public.

The team’s focus right now is on delivering an impactful and feature-rich Bernoulli release by the end of December, 2018. The focus in Bernoulli will very much be the database itself, and on providing further fundamentals to ensure it is able to provide a robust ecosystem that is decentralized and trustless. Following is an updated list of the most important features we have slated for Bernoulli:

PBFT consensus . This is the critical aspect of a trustless decentralized network — the ability to leverage computing resources that are under-utilized and that come from unknown sources, in a way that provides scalable utility to the network, but such that bad actors cannot attack the network or unfairly profit from it.

. This is the critical aspect of a trustless decentralized network — the ability to leverage computing resources that are under-utilized and that come from unknown sources, in a way that provides scalable utility to the network, but such that bad actors cannot attack the network or unfairly profit from it. Permissioning . A major improvement with Bernoulli will be the permissioning of writes to a namespace (defined by the UUID). More specifically, every user of the database will be required to have a public/private keypair on their client machine. The private key will be required to “sign” every write request (CREATE, UPDATE, DELETE). The Bluzelle network will consider a namespace’s first writer to be its owner, and henceforth, only that owner can write to it. The owner will also be able to assign ownership to another public key with a similar “signed” request. Down the road, the ability to have hierarchies and permissions associated with multiple owners and types of owners will be added.

. A major improvement with Bernoulli will be the permissioning of writes to a namespace (defined by the UUID). More specifically, every user of the database will be required to have a public/private keypair on their client machine. The private key will be required to “sign” every write request (CREATE, UPDATE, DELETE). The Bluzelle network will consider a namespace’s first writer to be its owner, and henceforth, only that owner can write to it. The owner will also be able to assign ownership to another public key with a similar “signed” request. Down the road, the ability to have hierarchies and permissions associated with multiple owners and types of owners will be added. Decentralized discovery of Bluzelle nodes , so that getting started as a client of the database (in any language) does not require prior knowledge of any node-specifics, such as IP address, port, etc. This is an elegant solution that uses Ethereum to achieve true decentralization of the discovery process.

, so that getting started as a client of the database (in any language) does not require prior knowledge of any node-specifics, such as IP address, port, etc. This is an elegant solution that uses Ethereum to achieve true decentralization of the discovery process. Our GUI CRUD client , that has been demoed to the public at various events and is used in our videos, will become available to the public. It will exist for all major operating systems as a desktop executable. We will also provide a version of it that runs on the web, available to members of the public that prefer a web interface.

, that has been demoed to the public at various events and is used in our videos, will become available to the public. It will exist for all major operating systems as a desktop executable. We will also provide a version of it that runs on the web, available to members of the public that prefer a web interface. Support for data syndication via our publishing toolkit and marketplace API. These tools will be the starting point for the Bluzelle data economy, enabling data syndicators to publish their data to our testnet while consumers can browse the marketplace to discover syndicated datasets.

The Bluzelle team has also put out blogs and detailed live demos performed by team members, that show how to use the Bluzelle database in different programming environments ranging from Ethereum Solidity to node.js. The team will also be putting out other videos that are typically technical in nature that provide < 45 second answers to commonly asked questions, topics, etc. Look for these on our blogging website at blog.bluzelle.com.

Important Note

If you have not already done so, note that Bluzelle has completed its transition from Slack to Gitter. Please sign onto Gitter and join the “Bluzelle” community to participate. Bluzelle’s community Slack has been phased out and will no longer function.