To me one of her key points is the FUD about Lisk dapp zip files. She is saying that because Lisk dapp files are not permanent fixtures on the Lisk mainchain (as ETH dapps are on the ETH mainchain), how do you know you are loading a clean Lisk dapp from a zip file you get from elsewhere? This is actually a valid point. So...does the capability exist now in Lisk to put in the main Lisk blockchain during dapp registration an MD5 hash or similar for the offchain Lisk dapp zip file? Can such a capability be added? Is should such a capability needed? (I think yes...)
A dapp dev can put a hash in the dapp description field and the users can control the hash before using the dapp. However, this is not feasible or elegant. Long-term I would like to introduce a "version scheme" into the dapp store. That means for every update the dapp developer has to upload a hash to the blockchain and before launching the dapp the Lisk client checks if the hash is correct. It's just a thought right now, but I'm pretty certain that we will implement something like that later on.
It's kind of ironic that as soon as I posted the response on StackOverflow there are immediately a few trolls here.
Take a look at Factom. They are leading in providing proof of existing, - process, - audit.
Thread:
https://bt.irlbtc.com/view/850070.0HP:
https://www.factom.comFactom is able to handle mountains of data and anchors in other Blockchains (Bitcoin first of course) to secure and proof itself. In my eyes a nearly perfect solution to be stable as a rock and very flexible and scalable at the same time.
Maybe you'll find a solution that is similar to Factom's design or maybe it would make sense to use Factom for Lisk-Dapp's, maybe even some kind of partnership would be possible. They partnered with a lot of Crypto-projects and also exchanges (Poloniex for example records data into Factom).
Current usage statistics:
https://docs.google.com/spreadsheets/d/1RUZLxxoAfT3C5jIJ144DLYdztYe_sqrKqbTlZuD05-s/edit#gid=445871101