With Ethereum, programmers now have the ability to develop all sorts of application in the blockchain, with all the desirable features it entails, such as trusted computation and global timestamping. There is, however a cost, both monetary and temporal to have application running on blockchains such as Ethereum, since it is essentially a slow, expensive global computer.
Hypercerts aims at striking a balance between what parts of the project run in the blockchain and what parts can be ran elsewhere (eg. cloud computing services such as AWS).
It could be interesting to investigate if there is a way to abstract how this balance can be achieved and create a general guide, that could be followed for a number of different applications.
With Ethereum, programmers now have the ability to develop all sorts of application in the blockchain, with all the desirable features it entails, such as trusted computation and global timestamping. There is, however a cost, both monetary and temporal to have application running on blockchains such as Ethereum, since it is essentially a slow, expensive global computer.
Hypercerts aims at striking a balance between what parts of the project run in the blockchain and what parts can be ran elsewhere (eg. cloud computing services such as AWS).
It could be interesting to investigate if there is a way to abstract how this balance can be achieved and create a general guide, that could be followed for a number of different applications.