Welcome to Bluzelle’s first update of 2018, following our Christmas-day update in late 2017!

We have some exciting updates and expansions on the development strategy. As previously mentioned, the database comes in many components. The component list includes the following:

Farming Daemon. Currently available to the public on Github.

GUI Client (to perform Creates, Reads, Updates, Deletes) to connect to the database. Will be released to the public as binaries initially.

GUI Admin Tool (internal tool to view low level details about nodes in a swarm). No public release initially.

Swarm Emulator (proprietary tool to deploy Bluzelle swarm networks for testing, diagnostics, and integrations). Will be released in binary form to partners and integrators.

RESTful web-sockets API (to connect to any node, emulated or not, and perform CRUD operations directly) in layer 5.

Javascript libraries (an abstraction for node.js and web app developers to use Bluzelle painlessly without having to use the API directly).

The most complex component is the farming daemon, which is what will ultimately go into production for the Bluzelle network to drive the nodes that are the basic building block for each swarm.

As a testing reference tool as well as means for developers to be able to build their own libraries (like the Javascript library) that can talk to the Bluzelle network, the Swarm Emulator is being built to lead and parallel the Farming Daemon. The Swarm Emulator represents the correct behaviour for the network, via emulation on a single machine.

More specifically, a single machine running the emulator is capable of representing all the nodes in a swarm, with the correct, reference behaviour. The emulator provides the the daemon development team with the opportunity to have preset unit tests (already used against the emulator) to test with to validate the correct behaviour of the daemon in a variety of use case scenarios set down by the emulator team.

More importantly, the emulated swarm gives the public earlier access to the swarm’s RESTful web-sockets API. This allows the public early access to a reference model of the swarm that they can integrate against. This enables other blockchains and platforms to build plugins and libraries to connect their environments with Bluzelle, even while the daemon is being developed, but with the knowledge that what they build works with the daemon just as seamlessly. The demand by 3rd parties to be able to write apps and libraries to talk to Bluzelle is high. The emulator will provide these 3rd parties with the means to build their codebases and decouple heavy and unnecessary dependencies on daemon releases.

Bluzelle will be deploying the emulated swarm with API access in coming months. This will be highlighted in a blog post update, giving information on the endpoints to connect to for the RESTful API’s, as well as the API documentation for the CRUD interfaces. Once this is ready, the public can immediately start integration efforts. We look forward to seeing contributions coming in, in the form of 3rd party plugins and integrations for programming languages and platforms.

In parallel with the emulator, the daemon team is hard at work building the initial single-swarm version of the database, that will thereafter expand into the metaswarm. While the emulator itself will not be immediately available on Github, the daemon team will continue to put out farming daemon updates to Github. Look for incremental updates on the devel branch and major updates on the master branch. Note that Bluzelle’s daemon team will keep smaller updates and commits off Github and limit updates to devel and master to squashed commits in an effort to keep the update history clean and organized.

Please stay tuned for updates on access to the emulator. And as usual, keep connected with Bluzelle via our many channels, including Github, where you can always access our latest public updates of the farming daemon and be able to deploy your own private swarms.