IPFS & HTTP: The Blueprint for Radical Interoperability
summary
Claim: HTTP becomes a first-class transport for IPFS rather than something to replace, demonstrated by a working demo that used trustless Gateway responses plus delegated routing to discover direct providers and fetch a CID over plain HTTP, with client-side verification via Helia verified Fetch. Subdomain gateways fixed web origin issues, a public delegated endpoint (delegated.ipfs.dodev) streams NDJSON provider results, and planned work adds HTTP retrieval into boxo and Rainbow plus HTTP multiaddr signaling to let ordinary HTTP servers serve IPFS blocks via range requests.
AI-written summary · about
chapters (9)
- 0:00Introduction to interoperability
- 1:11Evolution over revolution in web tech
- 2:37Subdomain gateways and browser compatibility
- 4:25Demo of delegated routing queries
- 6:34Future of IPFS and HTTP integration
- 9:03Incentives for HTTP exposure
- 10:49Direct retrieval and provider strategies
- 11:54How to try IPFS with HTTP today
- 13:20Endgame for IPFS and HTTP retrieval
