lxmf-protocol

LXMF messaging over Reticulum requires creating LXMessage objects, configuring an LXMRouter instance, and defining RNS destinations. The Skill provides protocol knowledge for handling delivery methods (DIRECT, OPPORTUNISTIC, PROPAGATED), stamps, tickets, and propagation node behavior to deploy robust networked messaging applications.

LXMF supports three delivery methods: DIRECT sends messages point-to-point via immediate RNS paths; OPPORTUNISTIC queues messages for delivery when paths become available; PROPAGATED routes through configured propagation nodes for resilience. Choose based on latency tolerance and network topology.

Yes. LXMF is a messaging protocol built on Reticulum (RNS) for routing and delivery. You must install and configure Reticulum alongside the LXMF toolkit to establish destinations, manage network identities, and route messages across the network.

LXMRouter configuration depends on your role: as a client, define destination identities and select delivery methods; as a propagation node, configure message queuing and rebroadcast behavior. The Skill provides practical examples for stamps, tickets, and router policies for real-world deployments.

Stamps and tickets are LXMF protocol mechanisms: stamps authenticate message origin and delivery claims; tickets track delivery status and enable acknowledgment workflows. Both are essential for building reliable messaging systems with proof-of-delivery and anti-spam properties.

Use propagation nodes when endpoints are intermittently connected, operate behind NAT, or need message persistence. Propagation nodes queue and redeliver messages, making OPPORTUNISTIC and PROPAGATED delivery methods suitable for mobile, offline-first, or poorly-connected network topologies.