Alternative Frontends, a Summary of Our Talk at Censorship.wtf DevConnect | by OKcontract | Nov, 2023 | Medium

In this post, we unpack the key takeaways from our talk at censorship.wtf during DevConnect, focusing on the crucial role that multiple frontend options play in enhancing censorship resistance for smart contracts. Smart contracts stand as public goods, yet the applications built atop blockchains often lack true decentralization, making them vulnerable to regulatory censorship. Hence, there’s a rising demand for alternative or decentralized frontends. Our journey to censorship resistance begins with deploying frontends using services like eth.limo, which rely on multiple decentralized technologies: ENS, IPNS, and IPFS. The initial step involves generating build artifacts from source code and storing them on decentralized platforms like IPFS. But is this sufficient? Exploring deeper, we find that the artifact’s source code often links to a centralized API, for example, an EC2 instance. This leads us to the anatomy of a typical web3 project: Note, that the client code is also generally re

In this post, we unpack the key takeaways from our talk at censorship.wtf during DevConnect, focusing on the crucial role that multiple frontend options play in enhancing censorship resistance for smart contracts. Smart contracts stand as public goods, yet the applications built atop blockchains often lack true decentralization, making them vulnerable to regulatory censorship. Hence, there’s a rising demand for alternative or decentralized frontends. Our journey to censorship resistance begins with deploying frontends using services like eth.limo, which rely on multiple decentralized technolog