Skip to content
All guide chapters

Packets across hops

How encrypted packets move hop by hop, and why plain traffic stays local.

Packet wireframe

Packet wireframe

Every Reticulum packet carries flags, a hop byte, a 16-byte destination hash, context, and payload. Header type 2 also carries a transport ID so relays can rewrap multi-hop data.

  • Header types 1 and 2 are both implemented in Reticulum-Go
  • Hop byte >= PATHFINDER_M (128) is rejected at unpack
  • This wireframe is conceptual. Exact packing lives in pkg/packet

Header type 1

Flags
Hops
Dest hash
Context
Payload

Type 2 adds a transport ID for multi-hop relay. Hops still face PATHFINDER_M at unpack.

Try it: Toggle header type 1 versus 2, then click each field. Notice Transport ID appears only on type 2.

Flags

1 bytes

Header type, packet type, and related flags that select how transport unpacks the frame.

Step 1 of 6

R
Reticulum-Go

A Go implementation of the Reticulum Network Stack. Building the future of resilient, sovereign communications.

Implementation License: Apache-2.0

Follow Development

Links

Quad4 Software

Backed by Quad4 Software. Building privacy-first, secure, efficient software.

quad4.io
© 2026 Quad4 Software. All rights reserved.
Deployed using Coolify