Development Road Map

We've named each of our major releases after a scientist/developer.


  • RAFT consensus. Trusted consensus amongst a fixed number of nodes run by Bluzelle.

  • Single swarm. All nodes are part of a single testnet swarm.

  • CRUD. Basic key-value-pair support.

  • JS client. Javascript and node.js applications.

  • Solidity client. Ethereum Solidity smart contracts via the Bluzelle bridge and Oraclize.

  • NEO client. NEO C# smart contracts via the Bluzelle NEO bridge.

  • Web sockets. Web socket connections from clients.


  • PBFT consensus. Trustless consensus support for arbitrary nodes in a single-swarm network.

  • Asymmetric keypair authentication. Security of namespaces enforced with owner and writer credentials.

  • Namespace metadata. Storage of metadata about namespaces to enable extended features such as security, governance, etc.

  • Peer-list server. Bootstrapping via an HTTP-powered peer-list server for clients and nodes.

  • Bluzelle Studio. A fully-featured web-application supporting CRUD access to namespaces with secured owner and writer security control.

  • Pub/Sub. Subscriptions to a namespace and publication of updates thereof, to clients.

  • Docker containers. Nodes can be deployed in fully-contained Docker containers on any major operating system.

MEIER release, May 2019 - COMPLETE

  • Smart caching. Data is stored using RAM and SSD. Cache features like eviction and expiry.

  • Multi-tenancy governance. Enable multiple customers to use the swarm with proper controls to protect data and ensure high availability and performance.

  • Multi-swarm. Data can be scaled using tiering across multiple geo-decentralized swarms worldwide.

  • Ethereum Swarm Registry. Auto-bootstrapping allows nodes and clients to discover existing swarms using the Ethereum mainnet.

  • StatsD. Aggregation and dissemination of swarm metrics, for monitoring and analytics.

  • External monitoring. Third party monitoring of Bluzelle nodes to ensure uptime, performance, availability, and other metrics are maintained.

  • JS and C++ clients. Full programming language support.

  • C++ common runtime. Base library to quickly develop support in new languages.

  • Bluzelle Studio. Updates to support multi-swarm and caching primitives.

  • Chaos module. Intentional entropy to harden the network preemptively against attacks, faults, load testing, and edge cases.

CURIE release, late October/early November 2019

  • Pricing. BLZ tokens are required to pay for and use services.

  • Trustless decentralization. Nodes operated by members of the public can join swarms. These farmers earn BLZ tokens for services provided.

  • Proof of Storage. Challenges to enforce governance of farming nodes and rewards.

  • Swarm-level geo-fencing. New swarms can have geographic properties, such as EU-only swarms and China-only swarms.

  • Native data types. Strings, sets, sorted sets, lists, hashes.

  • Ruby, PHP, Python, C#, and Java clients. Full support in these programming languages, using the C++ common runtime.

KEPLER release, May 2020

  • HQ Consensus. An upgrade to PBFT, where the performance of writes and strongly consistent reads is vastly improved.

  • In-place mutability. Functions on native data types, performed directly on Bluzelle.

  • Karma. Farmers can earn and lose karma based on performance and behavior.

  • Staking. Farmers are required to stake tokens inversely proportional to their karma.

  • Advanced token economics. Probabilistic payments to streamline payment and revenue models.

EINSTEIN release, November 2020

  • PaaS integration. AWS Elastic Beanstalk, Redhat OpenShift, Google App Engine, and Microsoft Azure.

  • IDE support. Integration of Bluzelle plugins into Android Studio, XCode, Xamarin, Visual Studio, Eclipse, IntelliJ IDEA, Unity3D, PhoneGap, and Ionic.

  • Import/Export. Tools to import and export data with legacy databases including MongoDB, MySQL, SQL Server, Oracle, Postgresql, CouchDB, etc.

  • Farming Appliances. AWS and Azure appliances on the marketplace, to allow quick farmer deployments.

  • Global ops. Read and delete functions on all values in a namespace.

  • Range queries. Read, update, and delete functions on ranges of keys.

  • Kubernetes support. Nodes can run as pods in a Kubernetes environment.