Skip to main content
Reticulum and Nostr are opt-in paths. Both require a working bridge and reachable external infrastructure. Enabling a configuration flag alone does not establish a path.

​
Reticulum

Use Reticulum through a deployment’s daemon or gateway. Its underlying links can include radios or IP networks; throughput and range depend on that infrastructure. The SDK does not give a phone a LoRa radio. Configure the daemon endpoint provided by your deployment and qualify authentication, framing, delivery verdicts and reconnect behaviour against the gateway contract. The Python manager’s default Reticulum callback is a stub. Supply the transport integration before claiming a working Reticulum path. Direct Rust integrations also provide their own I/O bridge.

​
Nostr

Nostr uses reachable WebSocket relays. It is an additional network path, not a substitute for a local radio when no network is available. Configure relays appropriate to the deployment rather than relying on an example public relay. The SDK seals Nostr envelopes by default. Keep sealingEnabled on: disabling it exposes the legacy protocol envelope to relay operators. Nostr startup requires the identity initialized by MLS.

​
What a relay observes

Sealing protects content, not all traffic metadata. A relay sees subscriptions, timing and traffic volume. A party that knows a device address can derive its routing tag. Evaluate that visibility against your deployment’s requirements. coldContactEnabled publishes and resolves key packages to support first contact. Disable it if that publication pattern is not appropriate; arrange another supported first-contact path.

​
Platform wiring

React Native contains native bridges. Verify the endpoint and device configuration on the target platform. Python’s default Nostr callback is a stub and needs implementation for a working path. For exact configuration and wire details, read the versioned Reticulum guide, Nostr guide and platform matrix. coldContactEnabled defaults to true, so key packages are published by default when the relevant path is enabled. usernameDiscoveryEnabled defaults to false; enable it explicitly for resolveUsername, together with cold contact. Reticulum requires a separately deployed gateway daemon; the SDK does not ship that daemon.