Thanks for the links. As I understand your approach might be summarized as (i) leave blockchain design intact e.g. Nakamoto’s strongest chain (ii) use the chain as a time stamping server so that it does not have to scale directly. Most of my research centers on scaling the total number of transactions and storage that a decentralized network can host. My work specifically is directed to scale-out networks that increase capacity as more participants join. The main aim is to build a decentralized cloud that can host critical infrastructure. One of the reasons we need this is that, if you cannot host all of the business logic as a protocol, you lose many of the benefits of decentralization. For example, one might imagine converting the business logic of Uber into a protocol represented by smart contracts in the decentralized cloud, with smartphone applications talking to it directly. If, for some reason the system instead depended on central servers the benefits would be lost, and the host of that server would ultimately need to spend billions of dollars negotiating with municipal councils, unions, regulators and so on just like Uber.