> Perhaps, it solves the trust issue of JavaScript. Yes, that is the intention :) > For the fun of it, maybe throw in some blocktrain tech or something to enh

> Perhaps, it solves the trust issue of JavaScript. Yes, that is the intention :) > For the fun of it, maybe throw in some blocktrain tech or something to enhance that trust model of yours. Instead of using GitHub as a public log, it's possible to use a publicly verifiable cryptographic log: https://wiki.mozilla.org/Security/Binary_Transparency https://wiki.mozilla.org/Security/Binary_Transparency That would move the trust from GitHub to that public log. However, GitHub provides us not just the "publicly verifiable update" part, but also the "authenticated update" part. In other words, how do you know that the person putting something in a blockchain is the owner of the website? You'd need a public key, and then not lose it, etc. But it's indeed possible.