A large payload is split into ordered, sealed chunks. Each takes its own path across the mesh and may arrive out of order; the far side reassembles them in order, deduplicated. Resumable after a gap.

How it works

A payload too big for one link is split into ordered chunks, each its own sealed, ACK-tracked datagram.
Chunks take independent paths across the mesh and can arrive out of order; the destination reassembles the original bundle, with id, acks, and dedup preserved.
Genuinely open-ended data (SSE, media) rides application streams instead, delivered in order, deduped, and resumable after a gap.

Why it matters

For developers

Carrier transport handles chunking and reassembly under one bundle id; the size cap is a sliding window, so a 5 MB image, or video, just works without any chunking code.

For business

Move files and media reliably across an intermittent network, not just short text messages.

Deeper implementation detail is coming in the Hop whitepaper.

← hps://HNS →

Carrier transport & streams

Ready to build on it?