That's all very well and good, but the larger problem with blockchains is that they're relatively heavy in terms of memory size. The article lists an example about Twister that is very compelling, in the sense that in order to use Twister, one has to download the entire blockchain to local memory first.

In a sense, this is a very real limitation of leveraging the power of the blockchain to end users - if anything, only entities that could afford dedicated resources would be able to do anything with it. This is all very well for treating the blockchain as a banking ledger, which might inevitably happen, but for distributed communication networks that have any level of activity on them, this could actually end up causing more harm than good.