Dev update

Hey, guys!

While Zano mainnet is getting ready we keep improving Boolberry, and quite a few changes were made recently.

Here we would like to highlight the most important of them for you:



2014 to present day and beyond


Boolberry is a cryptocurrency based on the Cryptonote protocol. At the time Cryptonote was created, most other cryptocurrencies were copies of bitcoin with a few parameters changed. Cryptonote was developed from the ground up to solve specific known issues with the many variants of Bitcoin that had flooded the market.

“Bitcoin” is the reference implementation of the bitcoin protocol. However, describing Cryptonote’s reference implementation becomes much more complex. There is a reference implementation of Cryptonote also called “Cryptonote” a currency that was never intended to be released into production, and an alternate currency called “Bytecoin.” This was the first production…

Dev update

After a long development process, we are finally ready to announce that Zano is nearing the release stage. Today, our team has prepared a short recap to showcase the project’s features, technical background, and much more, including a detailed explanation of Zano’s connection to our older project, Boolberry.

What is Zano?

Zano is our new blockchain project, primarily aimed at e-commerce related applications. While developing Zano, we have taken our previous experience into account, therefore Zano inherits some of the older technological principles that proved to be effective (e.g. CryptoNote). However, some of the features are developed completely from scratch.

Initial Blockchain Sync Speed Test Results / Guide

Changes in release V0.3.0.80 as was detailed in the August Dev Update:

As announced in the August Dev Update, the “predownloaded” version which requires running the daemon, was expected to be 24X improvement (1 hour for full blockchain synchronization). GUI implementation will be released in the coming weeks. See below for actual test results.

For those of you who want to test the speed, but prefer the GUI wallet, here is a short guide that walks you through the process.

Step 1: Install latest wallet…

Dev update

This month was all about one thing: Improving the initial user experience by optimizing synchronization speed.


There are trade-offs everywhere in crypto, and at every level! New “features” almost always have some form of trade-off or computational cost. For example: desktop wallets are more secure than exchanges or web / mobile wallet applications, but require the full download and synchronization of the blockchain. …

Dev update

July was a busy month full of key updates and bug fixes. We’ve fixed a bug with un-relayed transactions, solved a brutal pain point for restoring a broken wallet, speed up a syncing issue, and worked on general improvements across the board. Check out the details.

Fixed bug with un-relayed transactions

We’ve all complained about sending a transaction that went unconfirmed. One way this can happen is when the transaction gets sent while network connections are unstable and a connection is dropped. This means that the core and protocol have not recognized that the connection is broken while it’s waiting for a timeout. If this…

Dev update

With last month largely consumed by the development of an LMDB-based core, June ended up being a bunch of bug fixes and refinement. We dedicated a lot of time making this latest version stable. That included more improves to the GUI, like removing the lock_time field and refreshing the graphics in the GUI and the installer. We implemented load optimization, resulting in a 5X speed up in the daemon load time (made possible by improvements to our use of the scratchpad cache file). …

Dev update

Thanks for staying up to date on our progress,

Just a quick report this month as we’ve been heads-down on LMDB since we last checked in. With that said, our primary achievement in May was a stable LMDB-based version of our daemon and GUI.

Another milestone this last month was the implementation of an extended API for services and exchanges — letting services handle transactions in a more efficient way.


This last month also saw the implementation of method get_transfers. This feature is more effective than get_payments or get_bulk_payments, as it lets services specify transactions, filtering them by height. …

BETA launch

We’re excited to launch one of the key features of Boolberry, an aspect of our project that is crucial the decentralized nature of any Cryptocurrency. This cornerstone of our platform is the Boolberry Improvement Proposal System (BBIP) and we’ve just released the BETA.

We understand the value that comes from a committed community of stakeholders and continue to streamline the process for proposals. We’re looking for suggestions of all kinds. They can be feature related, designed to build awareness, promotional, and everything in between. Here’s how you can submit a proposal to shape the future of BBR.

Getting an alias

The first thing…

Dev update

What we’ve been up to

Okay, another month has flown by somehow and it’s time for an update on our development progress. A lot has been going on, but we’d like to call out one thing specifically, the implementation of LMDB. We decided to push LMDB ahead of schedule, deprioritizing listings, to make the project more appealing to the exchanges.

Up until this month, the entire blockchain has been loading into a RAM each time a user opens the daemon. Now, with the implementation of a database, we can speed up that process by only using RAM to process the changes in a blockchain.

LMDB Implementation details



Boolberry is a CryptoNote based cryptocurrency whose main goal is anonymity of the sender and receiver using unlinkable transactions.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store