Commons as a Service: Funding Shared Digital Infrastructure
Original title: Commons as a Service: Programmable Funding for Shared Digital Infrastructure
Watch on YouTube Opens on youtube.com in a new tab. Playback here uses youtube-nocookie.com.
Summary
The talk notes that crypto public‑goods funding usually relies on grants, retro funding and one‑off campaigns. It introduces Commons as a Service (CAAS) as a repository that routes a small, transparent share of on‑chain value to shared digital infrastructure. Design topics include who bears the cost—project, user or liquidity provider—where a source can be hosted, opt‑out defaults and how programmable routing removes trusted intermediaries. An example cited is the Keyring campaign that sent protocol fees to support Tornado Cash developer legal defense.
This AI summary uses the title, description and tags. It may miss context from the full video. How summaries are checked
Key points
- Public‑goods funding in crypto often uses grants, retro funding and one‑off campaigns
- CAAS is presented as a repository that routes a small, transparent share of on‑chain value to shared digital infrastructure
- Design considerations cover cost bearing (project, user, or LP), app surfaces for sources, opt‑out defaults, and programmable routing that eliminates trusted intermediaries
- The Keyring campaign is used as an example that directed protocol fees to fund Tornado Cash developer legal defense
A video appearing here is not an endorsement. Crypto assets can lose value. This page provides information, not investment advice.