Blockchain Trusted Websites

Mark Carey
Unwalled Garden
Published in
2 min readNov 5, 2017

The idea here is that the source code for a website is published to a public blockchain.

Based on my understanding, serving a website directly from a distributed blockchain isn’t technically feasible (at least with the “major” browsers) and even if it was, the load times would be too slow. Smart people are working on solutions for these issues.

In the meantime, this idea is for the source code to live on the blockchain, but it gets published to a web server and/or CDN, and that is where the website is actually served from. This aspect is no longer distributed, of course, and the server represents a single point of failure — the site could be taken down by the hosting company, attacked by hackers, etc …. just like a regular website. No, this isn’t the utopia of the distributed web. Not yet. A reasonable question is: what’s the point of the code being on the blockchain to begin with? The answer is trust. Because the code is on the blockchain, when we load the website in our browser, its possible to be sure, with confidence, that we are viewing the exact code as published on the blockchain. Perhaps this validation happens via trusted 3rd party script, or maybe a local browser extension. The idea is that user would get a verification that the website has not been tampered with and is indeed the site that has been distributed on the blockchain. Probably only valuable for certain types of websites or certain industries, I am not really sure.

--

--