I Built the World's First IPv8 Firmware Stack — Here's Why We Should Skip IPv6
Source: Dev.to
Why Skip IPv6?
IPv6 is 30 years old and still carries less than half of global internet traffic. Only 49 % of the world has adopted it, the US is just above 50 %, and a staggering 91.4 % of IoT devices break on IPv6‑only networks. The dual‑stack transition model—requiring every device, application, and network to support both IPv4 and IPv6—has proven commercially unacceptable.
The IETF draft draft‑thain‑ipv8 (published 14 April 2026) proposes a radical alternative: stop forcing IPv6 migration and build a protocol that works with IPv4, not against it.
- IPv8 is a 64‑bit protocol with a simple address format.
- IPv4 is a proper subset of IPv8—when the ASN prefix is zero, an IPv8 address is an IPv4 address.
- No dual‑stack, no flag day, no migration pain. Your existing IPv4 network already “speaks” IPv8; it just doesn’t know it yet.
I implemented the draft and created the world’s first IPv8 firmware stack, running on a standard laptop with zero hardware cost.
IPv8 Stack Features
| Feature | Description |
|---|---|
| IPv8 Addressing | 64‑bit addresses with ASN dot notation |
| DHCP8 | Single discover request returns address, DNS, NTP, auth, telemetry, routing |
| DNS8 | Resolver that requests both A (IPv4) and A8 (IPv8) records |
| OAuth8 | Device authentication via JWT tokens from the Zone Server |
| NetLog8 | Real‑time telemetry pipeline |
| XLATE8 | IPv4 backward‑compatibility translation |
| Zone Server | Central brain running all services on a single platform |
Boot Sequence
The boot process is intentionally simple: the Zone Server boots first, then devices discover their configuration via DHCP8 and start communicating using IPv8.
IPv8 vs IPv6 Quick Comparison
| Aspect | IPv6 | IPv8 |
|---|---|---|
| Address size | 128‑bit (overkill) | 64‑bit (enough) |
| Backward compatible | No | Yes — IPv4 is a subset |
| Dual‑stack required | Yes | No — single stack |
| Address format | 2001:0db8:85a3::8a2e:0370:7334 | 64496.10.0.0.100 |
| Header size | 40 bytes | 24 bytes |
| Management | Fragmented (separate DHCP, DNS, NTP, auth) | Unified Zone Server |
| Hardware change | Often required | Software‑only update |
| Years of effort | 30 years |
Roadmap
- ESP32 port via QEMU emulator (free, no hardware)
- lwIP fork with
AF_INET8socket support - Device‑to‑device IPv8 packet routing
- Web dashboard for Zone Server telemetry
- Real hardware testbed (2 × ESP32‑S3, ~₹1600)
Conclusion
IPv6 tried to replace IPv4 and, after three decades, still lacks widespread adoption. IPv8 takes a different approach: it embraces IPv4 by making it a subset of a new 64‑bit address space. This eliminates the need for dual‑stack deployments and dramatically simplifies network management—especially for the projected 60 + billion IoT devices.
The IPv8 firmware stack is open source under the MIT license and serves as a proof‑of‑concept implementation of the week‑old IETF draft. While not production‑ready, it demonstrates that a simpler migration path is feasible.
Star the repo if you’re interested: