dApps: How Unstoppable Are They?
summary
Uniswap keeps core logic as smart contracts on-chain (no owner controls), while its UI runs via Cloudflare + IPFS front end with each IPFS hash published to GitHub; token lists sit on IPFS but gateways add central points. Best-route computation uses a Node.js route finder on AWS (open source but a single-host failure hurts UX), and blockchain access relies on Infura RPC centralization, which is the biggest single stoppage risk. No server-side DB (only localStorage), and alternatives explored include FAA aash and acist for decentralized compute and Oasis Network for TEEs and encrypted on-chain keys.
AI-written summary · about
chapters (4)
related talks
16mIPFS and Dapps: Obstacles and Opportunities
19mThe Immutable Web
25mJavaScript Apps Going Inter-Planetary
14mResilience or Building on Quicksand: Decentralized Infrastructure
26mLaunch your dApp on decentralised Cloud
45mHow to build decentralized serverless html5 applications
27mWeb3 for Fun and Profit
39mA Universal "Hostless" Substrate for a Post-Serverless Futur
