F33-MT: No
Rationale
ReliableRouter adjusts retry deadlines for packet airtime, and NextHopRouter schedules attempts with a finite remaining-retransmission counter. At exhaustion it reports MAX_RETRANSMIT for locally originated traffic and removes the pending packet. The selected mechanism does not suspend recovery on loss of a prolonged contact opportunity and resume the retained transfer when contact returns.
Assessment method
Pinned firmware source and primary documentation; no runtime test
Source context
Selected Meshtastic ordinary CLIENT composition
Outstanding qualification
Airtime adjustments, channel-utilization-sensitive timeouts, initial duty-cycle rejection handling and final flooding fallback are real adaptations, but address local transmission conditions and bounded retries. They do not establish F33 contact-aware recovery. Store-and-forward is disabled in this composition. No unlimited outage tolerance or new RF experiment is claimed, and ordinary reliable messaging remains credited.
Public sources
- https://raw.githubusercontent.com/meshtastic/firmware/8e6a88d06f44cad26f1e8d7cd402939ccacb9b4c/src/mesh/NextHopRouter.cpp
- https://raw.githubusercontent.com/meshtastic/firmware/8e6a88d06f44cad26f1e8d7cd402939ccacb9b4c/src/mesh/ReliableRouter.cpp
- https://meshtastic.org/docs/overview/mesh-algo/
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round482.html
- round482-sources.json