Serving resilient multipath engagement

Taurnet 1.0 bonds satellite, cellular, and fiber paths with hybrid QKD and post-quantum keys — turning laboratory telemetry into live bonding, Bell-state routing, and BB84 sifting on Æ Hive infrastructure.

Top enterprise connectivity

Innovation lands when sessions survive path loss. Explore Taurnet 1.0 capabilities recognised for multipath bonding, quantum security, and traffic intelligence at the edge.

Taurnet 1.0™

Live laboratory console — bonding status, path inventory, Bell-state optimize, BB84 generate.

1.0

MPTCP bonding

Round-robin UDP across satellite, cellular, and terrestrial interfaces with scheduler weights.

RFC 8684

Hybrid QKD / PQC

BB84 sifting when quantum channels exist; ML-KEM and ML-DSA when they do not.

FIPS

Bell-state picker

Laboratory path selection from 00 vs 11 histograms — 1024-shot snapshot.

1024

POST /api/taurnet/*

Same-origin proxy — /api/bonding, /api/quantum, /api/qkd to CDNER-X backends.

PROXY

Bonded throughput

Active laboratory session: 250 Mbps aggregate with 15 ms latency probe.

250 Mbps

Smarter impact powered by Æ Hive

Maritime

Continuity across LEO beam hand-offs and coastal cellular with bonded satellite paths.

3 pathsbonded mix
Remote mining

Hybrid QKD/PQC protects operations data when satellite QKD is demonstration-stage.

QKD+PQCsecurity stack
Enterprise backup

Shift load to fiber or 5G before the primary path fails — scheduler reinjection on HOL blocking.

15 mslatency probe
Æ Hive Research · Quantum Multipath Bonding

The new economics of bonded connectivity | 17 September 2026, 11 AM ET

Learn how network, security, and operations leaders scale multipath sessions with QKD-aware fallbacks and auditable key-type records.

Register for live briefing

API Taurnet 1.0 · GET /api/bonding/* · POST /api/quantum · /api/qkd

Same-origin proxy at /api/taurnet forwards JSON to the Quantum Multipath Bonding backend (CDNER-X compose on port 8003 by default). Endpoints include /health, /api/bonding/status, /api/bonding/sessions, /api/bonding/start, POST /api/quantum/optimize, GET /api/quantum/results, and POST /api/qkd/generate. Console falls back to manuscript laboratory snapshots when backends are unreachable. Read the Taurnet 1.0 API documentation for fundamentals and interlinks.

Quantum Multipath Bonding — research dashboard

Laboratory console compiled from the bonding engine, Bell-state path picker, and BB84 sifting service. Snapshot sources for manuscript figures. doi:10.5281/zenodo.22219465

Connecting to Taurnet 1.0…

LINK
THROUGHPUT
LATENCY
ENGINE

Figure source A — lab telemetry

Lab telemetry tiles and bonded interfaces

Figure source B — four-plane architecture

Intelligence, security, control, and data planes

Figure source C — bonded paths

Session to scheduler to three paths

Figure source D — Bell-state counts

Bell state histogram 00 versus 11

Latest selection: Fiber · 00=479 · 11=545

Figure source E — BB84 sifting

Alice and Bob basis agreement

Table source — path inventory from the bonding service

PathKindBindTarget
Starlinksatellite127.0.0.1:9001127.0.0.1:10001
5Gcellular127.0.0.1:9002127.0.0.1:10002
Fiberterrestrial127.0.0.1:9003127.0.0.1:10003

Listing source — Bell-state decision (control excerpt)

qc = QuantumCircuit(2, 2)
qc.h(0)
qc.cx(0, 1)
qc.measure([0, 1], [0, 1])
# if C(00) > C(11): first path else last path
selected = paths[0] if counts.get("00", 0) > counts.get("11", 0) else paths[-1]

Bell-state sampling preferred Fiber over the remaining bonded paths.

Sources: bonding status, quantum optimize, QKD generate via /api/taurnet proxy · AE Quantum Research Division

Stay connected

What's New at Æ Hive — Taurnet 1.0 releases, multipath bonding research, and DCN security news.