in my talk i want to talk about the decentralization aspect of web3 frontends. our smart contracts are decentralized, permanent, censorship resistant and forkable - but what about our frontends? what about the user interfaces that most people actually use to interact with the contracts?
right now, most 'web3' frontends are just a next.js app running on a centralized vercel (read AWS) server somewhere (yes most of them use a server). not so web3.
so, an outline:
- the current state of most 'web3' frontends, what's wrong with them.
- why running everything on the client-side is important for a dApp (no servers! i'll talk about why trusting servers for frontends is a really fucking terrible idea and the fact that you don't even need one for a dApp)
- how you can deploy an actually decentralized and permanent web3 frontend (i'll deploy a react app to arweave live)
- making our frontends easily forkable and self-hostable (in the spirit of open source software and compasiblity)
- ideas about further improving the security of these frontends through cryptographically verifiable deployments.