The Block Lattice pt.3 – Adaptability

Part 3, in the previous blog we have taken a closer look at some of the inner workings, this time let’s look at how suitable and scalable the block lattice is and whether it is ready for long term adoption.


Block Lattice – Suitability for Developers

API support for Nano is quite good. They have RPC libraries, for interacting with nodes in Javascript, Python, PHP, and Elixir. They are all endorsed and posted on their devtools website.

There is also a library for performing Proof of Work in the web browser, written in WebAssembly. They also have a few more tools for interacting with the protocol and a package for Fedora.

The Nano team appears quite responsive and open in their communication and willing to help upcoming projects.


Suitability for IoT

Internet-of-Things-Needs-IPv6 - mini.png

Block Lattice Connects Everything

Nano provides a great use case for micro-transactions in the Internet of Things space. We will definitely need to utilize fast, free, miner-less blockchain technologies if we want our machines to quickly and autonomously interact with currency.

Data streams

Nano does not have a built-in mechanism for data transfer on layer 1, but there is an idea to use steganography, meaning that you could encode data inside the value transaction itself, since Nano uses 128 bits per transaction. In principle, you could use the bottom 64 or 32 bits to create and extract small messages.

Beyond that, Nano could implement a layer 2 approach pretty simply: if one can already communicate with other IoT devices, one could just utilize that channel for the data layer. Therefore, this does not appear to be a major obstacle for Nano.

Off-chain Transactions

With Nano, off-chain transactions are not entirely possible. The sending party must be online and connected to the network to facilitate a transaction, however the receiving party does not have to be online at this time, they will simply receive and process the transaction the next time they are online.

Personally, I don’t think this is a big issue, as there would still be a trust issue if it did have this feature. Beyond that, most smart devices and smart consumer electronics have internet access these days and since transactions in Nano using the Nano or Canoe wallet are virtually instant the amount off time one need to spend online to do a transaction is negligible.

Block Lattice Long Term Adoption

One issue that we will run into is that when there are enough users and clients of a cryptocurrency, we have to start asking ourselves, are there enough to go around? On top of that, when we are dealing with IoT where machines will send tiny amounts of a currency to each other, we need to make sure that these tiny amounts don’t grow too expensive in the long run.

Nano is effectively pre-mined, I.e. their ledger starts out with a fixed amount of cryptocurrency that can never change. Over time these tokens are being bought, sold, and moved around with ICOs and Faucets, increasing the general users’ attainment of these cryptocurrencies.

Also keep in mind that the amount of Nano in circulation is quite massive, perhaps not so interesting from a HODL perspective since there is a large circulation but certainly a plus point when it comes to use as a currency and for IoT interaction.

The maximum supply of Nano is on the order of 2¹²⁸ ~ 340e36, or 340 undecillion. The reason for this high ceiling is that they utilize a 128 bit integer to represent balances. Their actual max supply is about 133,248,290 MXRB, where 1 MXRB represents 10³⁰ (or 1 nonillion) raw Nano units.

The max supply can be denoted as roughly 133e36, or 133 undecillion raw Nano. Their wiki also denotes a few helper units based on the SI system to help with using some of these high numbers. Here is the maximum supply in raw units: 133,248,290,000,000,000,000,000,000,000,000,000,000. That’s 39 digits!

For comparison, this means there are about 48 sextillion raw Nano for each and every IOTA that could ever exist. IOTA (Tangle) has a maximum supply of roughly 2.8 quadrillion MIOTAs, whereas Bitcoin has a maximum of roughly 2.1 quadrillion satoshis.

Let’s picture a scenario where we reach 75 billion IoT devices by 2025. Let’s forget, to keep things simple, that there will be billions of people owning cryptocurrencies by 2025. Therefore, let’s also assume that these IoT devices own all the crypto.

Now, let’s make a few calculations. The average amount of crypto that will be shared among these future 75 billion devices will be on the order of 37 thousand IOTA (or 37 kIOTA) or 1.78 octillion raw Nano (or 1.78 kXRB); from this we can see that there will be much more flexibility (in terms of transactions) for Nano than either the Tangle or most of the traditional Blockchains/cryptocurrencies.


Block Lattice Scalability

Block Lattice scalability - mini.png

Scalability and Growth

Speed of Transactions

In Nano, the user performs the confirmation by signing their transaction. This process takes a trivially small amount of time. In general, your transaction is fully confirmed and processed in a matter of seconds. The bulk of the time is spent on performing proof of work, which is necessary to mitigate unchecked spam / DDoDs / Sybil attacks.

However, as soon in the Canoe demonstration video posted here ( transaction appear as close to instant as you can get, even with this pre-mining function. The whole transaction takes less than 20 seconds to fill out and as soon as you hit the transfer button the transfer appears instantly in the receiving wallet.

You can easily try this out for yourselves by downloading the Nano desktop and mobile wallet (or the canoe wallets: by then creating a different wallet on each device (which takes less than a minute) and by collecting some FREE Nano from the Nano faucet (

You will see these Nano appear in your selected wallet within a second and you can then send them between your two wallets instantly, and the most beautiful part … all this is transaction fee free!

Ledger Size

In Nano, the current full ledger size is on the order of 3 GB. Not bad for two years worth of transactions.

Granted, Nano isn’t nearly as popular as IOTA yet, so we have yet to see how it will perform under extreme loads. Over time, size will definitely become an issue. There are plans of pruning the database, as all that is needed for consistency is the total balance in each of the block lattice’s blockchains. This pruning is on their roadmap.



Decentralisation - mini.png

Shared Power In THe Block Lattice

Nano has no central authorities managing transactions on the network and has had auto-peering since its release around September 2015. Therefore, we can deem it as being decentralised.

The only area where there might be a slight issue is in that of their representative system. This is a potential attack vector, whereby a malicious entity may buy up millions of dollars worth of XRB and carry out a voting attack.

This scenario is outlined on their Attacks wiki. Granted, it is “low” risk as the malicious party would have to effectively forfeit large sums of money to carry out this attack, on the order of hundreds of millions of dollars or ~50% of the market cap, as of this writing. I will also be addressing various attacks in the next blog.

Lastly, we have already addressed the use case for nodes in the previous blog:


Block Lattice And Smart Contracts

Nano currently does not have a design for smart contracts, their entire focus is on the block lattice following their mantra “do one thing, and do it well”; since they are a very small team (4 people) this is entirely understandable and absolutely the right approach. It is entirely possible that this becomes a roadmap item in future or that this is addressed by others through a fork.



Despite the lack of smart contracts, I still believe that the block lattice is well positioned to play a major role in the expanding blockchain space, it already addresses a large number of issues faced by the legacy systems and could very well be the replacement of theses systems (even though this doesn’t seem to be the team’s objective).

PART 4 –

Acknowledgements / References

  • Title page “Intelligent Solutions” courtesy of
  • Page header / footer “Abstract blue lights” created by Kotkoa –
Other references:

Read the original article on Steemit