What Is IPv8? Three Different Things With the Same Name

So, Is IPv8 a Real Thing?

Short answer: kind of, but probably not what you're picturing.

If you landed here after seeing someone on Hacker News or LinkedIn talking about "IPv8," you're not the only one asking. The name has been floating around for a few weeks and it confuses almost everyone. The reason is simple: three completely different projects all answer to "IPv8," and only one of them is even trying to be a next-generation internet protocol.

Let's untangle what IPv8 actually refers to, why it became a hot topic in April 2026, and what it means (or doesn't mean) for your network.

The Three IPv8s

Before we go deep on any single one, here's the shortlist:

1. draft-thain-ipv8 — a 2026 IETF Internet-Draft proposing IPv8 as a 64-bit successor to IPv4. This is the one that went viral.
2. Tribler IPv8 — a Python and Kotlin library for peer-to-peer overlay networks, maintained by TU Delft researchers. Completely unrelated to IP-layer addressing.
3. Historical IPv8 (Pip) — an early-1990s IPng candidate by Paul Francis. It lost to what became IPv6 and has been a footnote ever since.

Most news coverage is about the first one. So let's start there.

IPv8 as Proposed in 2026: The Thain Draft

On April 1, 2026, an Internet-Draft titled "Internet Protocol Version 8 (IPv8)" appeared on the IETF datatracker. The author, Brendan Thain, is not affiliated with any well-known working group, and the draft is an individual submission — meaning the IETF lets almost anyone upload one. It has no formal standing as a standard.

The proposal is ambitious. It tries to do three things at once: expand the address space, flatten the BGP routing table, and bundle network management into a single platform.

The addressing model

Instead of IPv6's 128-bit hex addresses, IPv8 proposes 64-bit dotted decimal addresses in the form r.r.r.r.n.n.n.n:

• The first 32 bits (r.r.r.r) encode a routing prefix — specifically, an Autonomous System Number.
• The last 32 bits (n.n.n.n) behave just like an IPv4 host address.

Every ASN holder would get 4,294,967,296 host addresses — essentially a whole IPv4 internet each. The draft also claims that when r.r.r.r equals 0.0.0.0, the packet is a normal IPv4 packet, so "IPv4 is a proper subset of IPv8."

The Zone Server

The more unusual piece is the proposed Zone Server, a centralized box that would handle DHCP, DNS, NTP, WHOIS, authorization, and ACLs all at once. Every manageable element in an IPv8 network would be authenticated using OAuth2 JWT tokens — at Layer 3.

Why the community tore it apart

If you read the draft in isolation, some of it sounds reasonable. In context, it doesn't survive first contact with actual network engineers. A few of the louder criticisms from Hacker News, IETF mailing lists, and LowEndTalk:

• The backward-compatibility story doesn't work. An IPv4 router reading a packet header with Version=8 will not magically parse the additional octets. "Zero modification required" isn't how protocol fields work.
• OAuth at Layer 3 creates a chicken-and-egg problem. You need to talk to an auth server to get a token, but you can't talk to anything until you have a token.
• Tying addresses to ASNs kills provider multihoming, makes address transfers painful, and would demand roughly a thousand times more ASN allocations than exist today.
• Parts of the draft reference vendor-specific tech like Cisco's PVRST, which is a non-starter for anything aiming at standards track.
• A GPTZero analysis flagged the document as 76% likely AI-generated, and several reviewers called it "vibe-written."

The consensus after a week of review: interesting as a thought experiment, dead on arrival as a standard.

IPv8 as a P2P Overlay: Tribler's Library

Now a totally different IPv8. This one predates the Thain draft by years and has nothing to do with the network layer.

Tribler's IPv8 is a Python (and Kotlin) library for building peer-to-peer overlays. The name is a nod to the idea that peers are identified by public keys rather than IP addresses — so in a sense, it's "addressing beyond IPv6."

What it actually does:

• Identifies peers by public key, not IP address
• Handles NAT traversal via UDP hole-punching
• Provides end-to-end encryption with forward secrecy
• Organizes peers into "communities" (named overlays for specific apps)
• Powers Tribler, a decentralized BitTorrent client with Tor-like anonymity

If you're building a distributed app and you hear someone say "we run on IPv8," they almost always mean this library. It runs on top of UDP over standard IPv4/IPv6. Your router doesn't need to know anything about it.

IPv8 in Internet History: Pip and the IPng Competition

A bit of context most articles skip. In the early 1990s, the IETF ran a competition to pick a successor to IPv4. Several proposals were assigned version numbers:

• IPv5 — an experimental streaming protocol (ST2)
• IPv6 — the winner, based on SIPP
• IPv7 — TP/IX, later renamed CATNIP
• IPv8 — Pip, Paul Francis's proposal
• IPv9 — TUBA

So the number 8 has been "taken" for over 30 years. This is partly why the 2026 proposal raises eyebrows — the draft doesn't clearly acknowledge that the version field value is already historically assigned.

What This Means for Your Network Right Now

Honestly, not much. Nothing changes.

• You still run IPv4, IPv6, or dual stack.
• Your routers still only speak those two protocols.
• No ISP has any plan to carry IPv8 traffic.
• The real pressure on network teams in 2026 is still finishing the IPv6 migration — federal deadlines, rising IPv4 lease costs ($35–60 per address), and cloud providers charging for IPv4 attachments.

If anything, the IPv8 conversation is a useful reminder that IPv6 adoption is still slow (around 44% global reach), and people are visibly frustrated. That frustration is producing proposals like Thain's, not replacing IPv6.

Quick FAQ

Is IPv8 an official successor to IPv6? No. IPv6 is still the current and only IETF-standardized successor to IPv4. IPv8 is one individual's draft, not an approved standard.

Should I start learning IPv8 for my career? Not as an IP protocol. If you work on distributed apps, Tribler's IPv8 library is worth knowing. If you want to be future-proof on internet protocols, finish your IPv6 fluency first — that's where the jobs are.

Will the Thain draft become a real thing? Very unlikely. Individual Internet-Drafts expire after six months unless they gain working-group support, and this one has not.

What should I search for instead? If you want real protocol evolution, look at IPv6 extensions (SRv6, segment routing), QUIC, and the ongoing work on post-quantum transport security.

The Takeaway

IPv8 is a great example of how a name can move faster than the thing it describes. There's no new internet protocol coming next quarter. There's a controversial draft, a useful P2P library, and a historical footnote — all sharing the same three characters.

If you were worried about having to re-architect your network for IPv8, you can relax. If you haven't finished your IPv6 rollout, though — that's the real homework on your desk.

References

1. draft-thain-ipv8-00: Internet Protocol Version 8 — IETF Internet-Draft (April 2026)
2. draft-thain-ipv8 datatracker page — IETF Datatracker
3. Tribler py-ipv8 repository — Tribler / TU Delft
4. IPv8: Peer-to-Peer overlay network — Tribler project page
5. List of IP version numbers — Wikipedia
6. Hacker News discussion on IPv8 draft — Community review, April 2026
7. IPv4, IPv6 … What Happened to All the Other Numbers? — ARIN Blog (2022)