LabHub

Blog

Decentralized & P2P Content Protocols in 2026 — IPFS Helia / libp2p / BitTorrent v2 / WebTorrent / Hyperdrive / Iroh / Filecoin / Arweave / Storacha Deep Dive

2026-05-16 · 20 min read · #decentralized#p2p#ipfs#helia#boxo#libp2p#bittorrent-v2#bep-52#webtorrent#feross#hyperdrive#hypercore#beaker-browser-rip#dat-protocol#hyper#iroh#number-0#banyan-storage#filecoin#storj-dcs#arweave#sia#akord#pintswap#web3-storage#storacha#nft-storage#web5#tbd55#jack-dorsey#deep-dive#english

한국어English日本語

Prologue — "decentralized" is a word that hides too much

In 2026, when people say "decentralized content," everyone hears something different. One person pictures an IPFS CID. Another pictures a torrent magnet link. A third pictures Arweave's "permanent storage" promise. A fourth pictures Filecoin's storage market. And someone, somewhere, is still pulling up an old Jack Dorsey Web5 slide — even though that project has barely moved since 2024.

This piece puts all of those terms on a single map. Which protocols are alive, which ones died (Beaker Browser, RIP 2022), which ones rebranded (web3.storage to Storacha, 2024), and which ones are still quietly shipping (Iroh, Helia, Boxo).

Let me front-load the core message:

Let's walk through them.

1. The 2026 P2P Content Map — Four Big Buckets

The easiest mental model is four buckets.

+----------------------------------------------------------+
|              2026 P2P Content Map                        |
+----------------------------------------------------------+
| 1. IPFS family (content-addressed, CID)                  |
|    - IPFS Helia (JS)                                     |
|    - Kubo (Go)                                           |
|    - Boxo (modular library)                              |
|    - Iroh (Rust reimagination)                           |
|    - libp2p (networking stack)                           |
|                                                          |
| 2. Hyper family (append-only logs)                       |
|    - Hypercore                                           |
|    - Hyperdrive                                          |
|    - Beaker Browser (RIP 2022)                           |
|    - Dat to Hyper rebrand                                |
|                                                          |
| 3. BitTorrent family                                     |
|    - BitTorrent v1 (1990s)                               |
|    - BitTorrent v2 / BEP 52 (2018, slow uptake)          |
|    - WebTorrent (browser JS)                             |
|                                                          |
| 4. Crypto storage (economic incentives)                  |
|    - Filecoin (verifiable storage market)                |
|    - Arweave (permanent storage)                         |
|    - Storj DCS (S3-compatible)                           |
|    - Sia / Akord                                         |
|    - Banyan Storage (on Filecoin)                        |
+----------------------------------------------------------+

These four are complementary. IPFS is for addressing and discovery, BitTorrent for bulk distribution, Hyper for append-only data streams, crypto storage for durability and incentives. Different problems.

A few neighbors that sit slightly off the main map:

2. IPFS — Protocol Labs, still evolving

IPFS (InterPlanetary File System) was started in 2014 by Juan Benet at Protocol Labs. The protocol is content-addressed: files are identified not by location (URL) but by the hash of their contents (CID).

Why that matters:

IPFS implementations in 2026

For years the two major implementations were Kubo (Go, formerly go-ipfs) and js-ipfs. Then 2023 changed the JS side.

The trend is clear: the IPFS world is moving from a single monolithic daemon to libraries you embed.

IPFS is not a blockchain

A persistent confusion worth squashing: IPFS is not a blockchain. There is no consensus algorithm and no token in the base IPFS protocol. IPFS is a DHT-based content lookup system.

Filecoin came out of the same company (Protocol Labs) and is the blockchain piece. IPFS is the address scheme; Filecoin is the market that pays storage providers to keep those addresses around.

3. Helia (August 2023) — The Modern JS Client Replacing js-ipfs

Helia is the JavaScript IPFS rewrite that Protocol Labs and the IPFS Foundation released in August 2023. It is closer to a from-scratch reimplementation than an incremental js-ipfs upgrade.

Why rewrite? Since js-ipfs started (2016), the JS ecosystem changed too much. ES modules, TypeScript-first, Web Streams, and above all, front-end environments where bundle size matters. The old js-ipfs codebase was large, heavy, and tightly coupled.

Helia's design principles:

A minimal Helia sketch:

import { createHelia } from 'helia'
import { unixfs } from '@helia/unixfs'

const helia = await createHelia()
const fs = unixfs(helia)

// Upload
const encoder = new TextEncoder()
const cid = await fs.addBytes(encoder.encode('Hello Helia 2026'))
console.log('CID:', cid.toString())

// Read back
const decoder = new TextDecoder()
let content = ''
for await (const chunk of fs.cat(cid)) {
  content += decoder.decode(chunk)
}
console.log(content)

When does Helia fit?

4. Boxo — Modular IPFS Library (Go)

Boxo is the Go library collection spun out of Kubo in 2023. The name is meant to evoke "a collection of boxes."

If Helia is the JS-side "modular IPFS," Boxo is the Go-side equivalent. Kubo is the full-node daemon; Boxo is the toolbox of components that Kubo uses internally, repackaged so other projects can use them too.

Components include:

When do you reach for Boxo? When you want pieces of IPFS embedded in your service, not a full node. Examples:

The Boxo split is the clearest signal of the IPFS world's drift from monolith daemon to embeddable library.

5. libp2p — The Networking Stack That Outgrew IPFS

libp2p was originally part of IPFS. Everything P2P networking needs — peer discovery, transports, multiplexing, encryption — bundled into a library IPFS used internally. It was good enough that people wanted it outside IPFS too, so it became its own project.

In 2026, libp2p is an essentially independent P2P networking standard. It is used by Ethereum 2.0 consensus clients (Lighthouse, Lodestar, Nimbus), Polkadot/Substrate, Filecoin, Eth2 P2P gossip, and Iroh.

libp2p modularity

libp2p's core idea is "transports and protocols are swappable":

JS sketch — roughly what Helia configures under the hood:

import { createLibp2p } from 'libp2p'
import { webSockets } from '@libp2p/websockets'
import { webRTC } from '@libp2p/webrtc'
import { noise } from '@chainsafe/libp2p-noise'
import { yamux } from '@chainsafe/libp2p-yamux'

const node = await createLibp2p({
  transports: [webSockets(), webRTC()],
  connectionEncryption: [noise()],
  streamMuxers: [yamux()]
})

await node.start()
console.log('peer id:', node.peerId.toString())

Learn libp2p once and you understand the internals of most modern P2P systems, not just IPFS. It is basically a standard.

6. BitTorrent v2 (BEP 52) — A 2018 Spec Still Slow to Adopt in 2026

BitTorrent v2 is the major upgrade specified in 2018 as BEP 52. The headline changes:

Technically v2 is unambiguously better. But in 2026 adoption is still slow. Why?

State of the world in 2026:

Who should care:

7. WebTorrent — Browser-Native Torrents in JavaScript

WebTorrent, built by Feross Aboukhadijeh, is a pure-JS, browser-native BitTorrent client. There is a desktop app too, but the magic is being able to download torrents inside a browser tab with no plugin.

How? WebRTC

Traditional BitTorrent uses TCP/UDP. Browsers cannot use either directly. WebTorrent uses WebRTC data channels as its transport, which makes browser-to-browser P2P possible.

Trade-offs:

A tiny browser snippet:

import WebTorrent from 'webtorrent'

const client = new WebTorrent()
const magnetURI = 'magnet:?xt=urn:btih:...'

client.add(magnetURI, function (torrent) {
  torrent.files.forEach(function (file) {
    // stream directly into a video element
    file.appendTo('#player')
  })
})

Why WebTorrent survived:

In 2026 WebTorrent is, in practice, the default library for WebRTC-based P2P video and live streaming.

8. Hyperdrive + Hypercore — Append-Only Logs as a Filesystem

Hypercore is a P2P protocol for append-only logs (logs you can only append to). Hyperdrive is the filesystem abstraction built on top.

Core ideas:

How is this different from IPFS? IPFS is for addressing already-finished data; Hypercore is for replicating data that grows over time. Different problem.

Hypercore fits when:

JS sketch:

import Hypercore from 'hypercore'

const core = new Hypercore('./my-storage')
await core.ready()

await core.append('first entry')
await core.append('second entry')

console.log('blocks:', core.length)
const first = await core.get(0)
console.log(first.toString())

9. Beaker Browser (RIP 2022) → Dat → Hyper Rebrand

Beaker Browser existed from 2016 to 2022 as a "P2P web browser." It looked like an ordinary browser but could host and visit P2P sites over dat://. Create a folder, hit "publish," and you had a P2P site.

In 2022 Beaker officially stopped development. But the underlying Dat protocol did not die — it rebranded to Hyper and lives on as a library ecosystem.

The Beaker-died-but-libraries-survive pattern is a recurring one in P2P history. Compare:

From the browser vendor side, P2P integration is so deep — across security and UX — that staying in library form is the realistic equilibrium.

10. Iroh (Number 0) — A Rust Reimagination of IPFS

Iroh is the Number 0 team's Rust-based IPFS reimagination. Started around 2022, moved fast through 2024-25.

Core message: "Keep the good ideas of IPFS, drop the baggage of the legacy implementations."

What distinguishes Iroh:

Iroh describes itself as "a library for moving files P2P, quickly." It follows IPFS ideas but does not try to implement every feature of the IPFS reference stack.

A Rust sketch:

use iroh::Iroh;

#[tokio::main]
async fn main() -> anyhow::Result<()> {
    let iroh = Iroh::memory().await?;
    let blob = iroh.blobs().add_bytes(b"Hello Iroh 2026".to_vec()).await?;
    println!("hash: {}", blob.hash);
    Ok(())
}

When to choose Iroh:

When to choose IPFS Kubo:

11. Banyan / Filecoin / Storj DCS / Arweave / Sia / Akord — Five Flavors of Crypto Storage

This section is about the economic model of where data lives. P2P protocols define how to address data, not who keeps the disks spinning — that is a separate market.

Filecoin

Filecoin (Protocol Labs) is the storage-market blockchain. The mechanism:

The big change from 2024-25 was FVM (Filecoin Virtual Machine) — EVM-compatible smart contracts on Filecoin.

Banyan Storage

Banyan Storage sits on top of Filecoin as end-to-end-encrypted cloud-storage UX. Regular users do not see Filecoin at all; they get something Dropbox-like. The backend is Filecoin and IPFS.

Storj DCS (Decentralized Cloud Storage)

Storj is a P2P distributed store with an S3-compatible API front and center. Key tricks:

The positioning is more "S3 replacement" than "Web3 storage." It is engineered for migration ease.

Arweave

Arweave is different. The keyword is permanent storage: pay once, "200 years" promised.

Common uses: NFT metadata, academic material, content that cannot afford to disappear.

Sia / Akord

Veera Network

Newer, eyeing P2P CDN and content delivery. Not yet mainstream.

One-liner matrix

SolutionOne-liner
FilecoinStorage-market blockchain paired with IPFS
BanyanUser-friendly cloud UX on top of Filecoin
StorjS3-compatible distributed storage
ArweaveBlockweave with "permanent storage" pricing
SiaOlder P2P storage with host-renter contracts
AkordUI layer over Arweave

12. Pintswap / Pollen — The Next Wave

Pintswap is a P2P token swap protocol. No central matching engine; OTC trades happen peer-to-peer over libp2p, with only the settlement signed on-chain.

Pollen Network is a P2P CDN vision — pooling spare bandwidth from user devices to serve content.

Neither is mainstream in 2026, but both illustrate the pattern of P2P infrastructure slipping into the lower layers of dApps.

13. web3.storage to Storacha (Rebrand, 2024)

From 2020 to 2022, web3.storage and NFT.Storage were Protocol Labs-run services that let you throw a file at them and they would store it on IPFS plus Filecoin, mostly free or cheap. Everything from NFT metadata to academic datasets ended up using them.

In 2024 web3.storage rebranded to Storacha, with operational responsibility splitting off. Key changes:

CLI in practice:

# install
npm install -g @web3-storage/w3cli

# log in (email)
w3 login your@email.com

# create a space
w3 space create my-space

# upload
w3 up ./my-file.png

Operationally, this is still one of the most approachable ways to host IPFS content.

14. NFT.Storage — Protocol Labs

NFT.Storage is the sister project focused on NFT metadata. Token IDs, images, attributes JSON — all parked on IPFS, originally free.

In 2024 NFT.Storage split into NFT.Storage Classic (free, minimal support) and NFT.Storage v2 (commercial). Free-tier policy changes put a small crack in the "free permanent NFT metadata" promise, and some collections moved to Arweave as a result.

The lesson: never trust a free IPFS pinning service to be permanent. Someone always pays the bill.

15. Web5 (TBD55, Jack Dorsey) — Stalled

Web5 is the vision Jack Dorsey's Block (formerly Square) and its TBD group (sometimes called TBD55) announced in 2022. The slogan: "Web2 usability plus Web3 decentralization, without tokens."

Design pillars:

The ambition was huge. Through 2024-25 the pace fell off sharply. As of 2026:

It is a useful case study in strong slogan, weak building momentum.

16. Korea and Japan IPFS Usage Notes

P2P protocols are global, but regional examples ground the picture.

Korea

Japan

Common thread: "NFT metadata plus permanent storage" is the scenario where IPFS and Arweave most often appear side by side.

17. Who Should Learn P2P Content?

RoleWhat to study
dApp / NFT developerIPFS (Helia), Storacha, NFT.Storage, Arweave
Distributed systems engineerlibp2p, IPFS Kubo, Iroh internals
Mobile / Tauri developerIroh, WebRTC, WebTorrent
Data archivistArweave, Filecoin, Banyan
Academic / researchIPFS, Arweave, Tahoe-LAFS
Censorship-resistance / human rights toolsIPFS, BitTorrent v2, WebTorrent, libp2p
Media / CDNWebTorrent, Pollen, Filecoin

Four reasons to learn it

  1. Permanent storage — content that survives the company that uploaded it. NFTs, academia, journalism.
  2. Censorship resistance — when single-host dependency is a problem. (And the responsibility, including for bad content, distributes too.)
  3. CDN cost reduction — P2P can dramatically cut egress for large content.
  4. The systems-design fun — libp2p, Iroh, Hypercore are excellent material in their own right.

When you should not use P2P

P2P is not a default; it is a tool for specific problems. Do not try to put it everywhere.

18. A 5-Minute Decision Tree for 2026

QuestionAnswer
Just want to drop a small file on IPFSStoracha (formerly web3.storage)
Hosting NFT metadataStoracha plus Arweave dual hosting
Real permanent storage (decades)Arweave
Drop-in replacement for S3Storj DCS
IPFS node directly in the browserHelia
Browser torrents or P2P videoWebTorrent
P2P file transfer on mobileIroh
Append-only collaborative dataHypercore / Hyperdrive
P2P in a Rust backendIroh or libp2p (Rust)
Censorship-resistant video platformPeerTube (ActivityPub plus WebTorrent)
P2P token swapsPintswap

Epilogue — What Survived and Why

Twelve years on from IPFS's 2014 launch, the P2P content space has seen one full cycle of hype and consolidation. The pattern of what survived is fairly clear.

Survivors share:

Those that died or stalled share:

The right 2026 stance is not "all-in decentralized" but "selectively P2P." IPFS for NFT metadata, Arweave for permanence, WebTorrent for browser video, and S3 for everything else. That mix is the pragmatic one.

References

Read the original: https://www.youngju.dev/blog/culture/2026-05-16-decentralized-p2p-content-2026-ipfs-helia-libp2p-bittorrent-v2-webtorrent-hyperdrive-iroh-filecoin-arweave-storacha-deep-dive.en

Comments

No comments yet.

Sign in to leave a comment