Managing Subscriptions in Web3
summary
On-chain subscriptions are hard because blockchains are push-based and approvals plus off-chain bots create trust, counterparty and gas-cost failures; streaming claims to fix that by having zero trust and zero counterparty risk — users open a stream with a single on-chain tx to open and close and then payments settle every second, letting merchants receive continuous, verifiable revenue, enabling capital-efficient services, undercollateralized loans against predictable flows, and composable subscription NFTs.
AI-written summary · about
chapters (10)
- 0:00Start
- 1:08Web2 payments
- 2:25Attempts at pull based systems
- 2:52Pull based on-chain payments
- 5:14The Beach Problem
- 5:31Streaming solves this
- 7:12Why streaming is better?
- 8:53On-chain composability
- 10:58Service composability
- 12:20What could subscriptions do for web3?
related talks
24mBuilding a decentralised pub/sub
05mHow Can Music Streaming be Shaken Up by Blockchain?
28mSimplifying Writing and Reading Transactions On-Chain - Applications and Miners
19mCrypto-Native Rails for Recurring Payments
56mweb3.js 1.0
44miOS Subscriptions are Hard
24mYou Don't Own Me: How Blockchains Are Creating Community Economies
57mProviding Real World Data to Blockchain