Cascade delivers the internet's biggest content โ video, downloads, files โ from the spare bandwidth of ordinary devices, and pays each one per parcel, in real time, on Kaspa. It is a decentralized replacement for the handful of companies that own delivery today.
Each stream is a parcel โ one verified, paid piece โ flowing from a different node; each gold flash is a micro-payment settling on Kaspa. An illustration of Cascade's real behaviour, pinned by tests.
Almost everything you load โ a video, an app update, a news site โ doesn't come from the website you visited. It comes from a cache near you run by Cloudflare, Akamai, or Amazon. This layer, the Content Delivery Network, is most of what makes the internet feel fast. It is also owned by a handful of firms โ and that concentration has a cost we've all paid.
None of this is villainy โ it's what happens when critical infrastructure is owned by a few. A single point of speed becomes a single point of failure, of billing power, and of control over what stays online. The delivery layer of the internet was never supposed to belong to five companies.
Cascade takes the one idea that has moved the internet's heaviest files for twenty years โ a Meridian, where many devices each hold pieces and you pull them from all at once โ and gives it the one thing it always lacked: a way to pay the people who serve. Torrents die because seeding is charity. Here, delivering a parcel earns money, so serving is a job, and the Meridian has a reason to exist. The bytes move device-to-device over the ordinary internet; only the payment touches the chain, and it's tiny.
Bytes from the crowd. Money to the crowd. No company owning the middle.
It doesn't match the hash you held before you asked, so it's refused, never paid for. The manifest is the referee โ no trust needed for delivery.
A parcel costs its size from the manifest, which you had before the request. A fount can't inflate it. Stop partway and you've paid for exactly what arrived, to the byte.
Cascade replaces the CDN โ the part of the cloud that moves finished bytes โ not the server that runs an app. And it competes on the publisher's bill: today a site pays Cloudflare to deliver its video to you; with Cascade it pays the crowd's spare bandwidth instead, for less. You still watch for free โ the crowd is paid, not you.
| Cascade delivers this | Cascade can't โ a server must |
|---|---|
| A video, a song, a podcast | Your personalized feed or inbox |
| A game or app download, an OS update | Search results, a checkout, a dashboard |
| Images, fonts, a site's JS/CSS bundle | The dynamic HTML built per request |
| A big public dataset; a fully static site | Anything private or per-user |
The rule is simple: Cascade carries bytes that are the same for everyone โ which happens to be most of the internet's actual weight (video alone is well over half of all traffic). Anything generated on the fly, just for you, stays on a server. The closest thing that exists is IPFS โ but with the real-time payment layer it never had.
A site funds a delivery budget in KAS โ exactly as it funds a CDN account today โ and gets a manifest for its content.
Spare bandwidth and disk. They cache popular parcels and serve them, earning per verified parcel. Serve junk, earn nothing.
Pulls parcels, checks each against the manifest, and signs a receipt. That receipt is a fount's proof it earned โ junk gets none.
The viewer is the meter and the referee; the publisher is the payer; the crowd is the earner. Cheating is caught for free, because a bad parcel never earns a receipt. It's a two-sided market where the money only ever moves for bytes that provably arrived.
A delivery network makes thousands of tiny payments a second โ one per parcel, per viewer, per fount. That's impossible if settling takes minutes and costs more than the payment. It's why every decentralized-CDN attempt so far either doesn't really pay per use, or batches it and leans on a speculative token โ quietly putting a trusted middle back.
Kaspa states its purpose as real-time decentralization: censorship-resistance and permissionless settlement in real time, not eventually โ on a fair-launched proof-of-work chain with no premine. It confirms in about a second at up to ten blocks a second. Cascade is that doctrine made physical: a network that pays its participants as they serve, continuously. The money keeps pace with the bytes. That's not a clever use of a fast chain โ it's the thing the fast chain exists to do.
The word "decentralization" gets worn smooth by crypto marketing, so here is the plain version. When the delivery layer of the internet is owned by a few companies, three things follow, whether those companies mean well or not: they can throttle or bill you at will, they can take you offline with a phone call, and when they break, everyone breaks at once. You are a tenant on someone else's infrastructure, and tenancy can be revoked.
Cascade changes the ownership, not just the technology. When the caches are everyone's devices, no single company holds the switch. There is no trust-and-safety desk that can un-publish a lawful site, no single outage that darkens a fifth of the web, no monopoly rent on moving bytes that cost the crowd almost nothing to move. The infrastructure belongs to the people using it โ which is what the internet was supposed to be before it consolidated into a few landlords.
This is what "reclaiming the internet" actually means in practice โ not a manifesto, a property change. The heavy content we all depend on gets carried by a commons the crowd owns and is paid to maintain, on money that no company or state issues or freezes. Sovereignty isn't a feeling here; it's whose hardware your bytes live on, and whose permission you need to be seen.
A commons the crowd owns and is paid to keep. That is the whole idea.
A claim is only worth as much as its caveats. Here they are, plainly โ because a project that hides its hard parts isn't one you should trust with the internet's plumbing.