Overview

How the pieces fit and how to embed them. Start with theQuickstart, then pick the driver for your platform.

How Hop is layered

hop-core is a pure Rust core: it seals, addresses, holds, and routes datagrams, but it has no bearer system of its own. It only moves bytes. A driver is the per-platform host that embeds the core and implements the bearer trait (send_frame /recv_frame / peer_events): it owns discovery, connections, background operation, and power for one platform.

Above the core sit the semantics (hops://, hps://,streams, HNS); below it, the bearers (BLE, Wi-Fi/LAN, the internet relay). See the protocol stack for the full picture.

Drivers

The hosts that run the core and drive the radios.

Background reading

Why a delay-tolerant mesh can't just run TCP/TLS end to end:TCP, TLS, and delay tolerance, an interactive primer.

Start building

Quickstart →

Hop is in early access. Request access and tell us what you're building. Building on a platform that isn't here yet? Tell us.