Bismuth Team progress report – May 2020

This report covers April 17, 2020 to May 17, 2020.
Read on below:

Core Node

No meaningful details to report here. Best place to keep up to date on the details is the Github hook channel on our discord. This is still a work in progress.

Most of the core work was related to Tornado Wallet, crystals and ecosystem, as you’ll read below.


Current Hypernodes ROI is 20.3%, slightly up from 20.2% in the last report. We count 233 active Hypernodes with a total amount of active collateral of 6,220,000 BIS.

Data from the Hypernodes page.

The plot below shows all Hypernodes, both Active and Inactive, during the last 60 days. As can be seen from the plot the number of hypernodes has been stable at 321 HNs during most of the last 30 days. This is a good sign, as the hypernode network continues to mature.

Total number of Hypernodes, both active and inactive.

The plot below shows the total Hypernode collateral, both active and inactive, during the last 60 days. As can be seen, the total amount of collateral has been stable during this period, especially during the last 20 days. The total amount of Bis in circulation is 23,9 million. Hence, the amount of active collateral accounts for 26.1% of the total supply, or 35.4% if the amount of inactive collateral is included.

Total amount of HN collateral, both active and inactive.


  • Upgrade of core libraries shipped by default with Tornado wallet: dataTables, jquery ui, Chart.js v2.9.3. This allows crystal developers to leverage local version of these tools rather than querying online CDNs and limits the potential data leaks as well.
  • Upgrade of Dragginator and Docshield crystals that were using CDNs versions.
  • Update of the “How to Use the Bismuth Tornado Wallet on Android Using Termux” tutorial. The latest version of Termux comes with Python 3.8. Instructions were simplified and adapted to this version.
  • New archive page displaying all articles. This page gives an overview of all Bismuth related articles posted by the team, and it makes it much easier to find older articles compared to going through the blog history.
  • Decentralized condition monitoring (and tweet). This article describes a new second layer protocol built on top of Bismuth to allow for decentralized condition monitoring. The operation and data fields is a very important feature of Bismuth, which distinguishes it from most other crypto projects.
  • Public website for docshield. This website makes use of a new feature of the Tornado Wallet (Read Only Mode – To be documented), which allows reuse of crystals for public websites. In this way, the hashes for protected documents can quickly be found without having to start up the Tornado Wallet on your local computer.
  • Android battery monitoring. (and tweet) This is the first crystal in the Tornado Wallet which makes use of the new second layer protocol for handling simple assets. The battery monitoring crystal can be run on Android phones using Termux, and there is also a public website for easy viewing of all the submitted data without having to start up the Tornado Wallet on your local computer,


A new chess tournament– with BIS prizes – was organized again by Damian

Interactions with other coins

Bismuth is built totally from scratch and comes with some innovative ideas and technologies. Some of them are the subject of academic papers, like the non linear difficulty feedback algorithm, or the tail removal. Others are more generic like the Bisurl encoding or the “operation/data” field to support dapps on second layer.

The BGVP (see here and here) is an innovative protocol which was very thought of.
Skin in the game, blind votes, predication market… have a read on the issues it solves. The protocol itself is public, as is our implementation of the tools and voting helper.

Some community developers at Idena did use this as a basis to create a PoC that could be part of Idena tools. You can see current repository here.

Our code is MIT, meaning the only requirement is to keep the license with our credits. The Bisurl concept also is being ported and improved, as “DnaUrl” and will evolve on its own with Dna specificity and improvements.

So – even though not obvious from the outside – Bismuth is a motor of innovation among other projects, can help quick-start things, and benefits in return from more exposure, feedback, and technical improvements.

We’re very proud of that.

Generic protocols also are very important because they allow some core principles – like the “operation” selector or our second layer execution model – to be used almost as is in other contexts. Idena supports data field as well, and is mostly compatible. Meaning it’s easier to adapt dapps built on these principles between these chains. this benefits everyone.
dapps creators, chains, users…