Plaintext at the ends, garbled (sealed) in transit. Copies take more than one peer path; each relay holds its stored copy until an acknowledgement comes back, then releases it. Held, never dropped.

How it works

Each datagram is born with a small copy budget that binary-splits across peers, copies fan out on independent paths in parallel (spray-and-wait).
Sealed and addressed to a key; relays carry ciphertext they can't read and keep custody of their copy until they've handed it onward.
The recipient's acknowledgement travels back as a vaccine, every node it reaches drops its copy and refuses more, collapsing the flood. Held when there's no route, never dropped.

Why it matters

For developers

One connectionless send/receive primitive, a sealed, addressed bundle. The library handles spray-and-wait replication, custody, retransmit with backoff, dedup, and the delivery-ACK; you manage no connections or routes.

For business

Messages get through across flaky or absent networks with nothing to operate. Delivery is eventual but guaranteed, with a default 24-hour lifetime everything above inherits.

Deeper implementation detail is coming in the Hop whitepaper.

← HNS BLE →

hdp://

Ready to build on it?