Implementing web3 via APIs is still decentralized?
summary
Argues that routing frontend → backend → public node → smart contract often improves UX while still leaving on‑chain logic decentralized, demonstrates an NFT marketplace prototype and an Angular helper library, measures that a naive frontend-only approach for three collections × six NFTs requires 30 smart contract calls and 18 HTTP requests, shows timings of under 1s with a backend vs 4s–16s when calling contracts directly, and lists practical tools used: ethers, MetaMask, public node providers (Alchemy QuickNode Infura), IPFS, JS/TypeScript.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 3:15Avatars
- 3:37Web3 as technology
- 4:28Pros
- 5:36Cons
- 6:26Web Tree
- 7:46Decentralization
- 11:39Frontend centralized
- 13:03Scalability
- 13:49NFT Marketplace
- 15:26Collection List
- 17:43Backend
- 21:19JavaScript
- 23:51Wallet Provider
- 25:08Wallet Provider Example
- 29:49Outro
related talks
30mFull Stack Web3 - The Technology Stack for the Decentralized Web
16mAlternate Frontends: Why and How
48mDesigning for Web3
20mA Frontend Developers Guide to Web3
06mReacting to Web3
27mThe importance of APIs within the Web3 ecosystem
44mBackend less Development revisited
45mThe Problems Micro Frontends Won't Solve That No One Wants to Talk About