G03-MT: Yes
Rationale
In the pinned Meshtastic firmware, a missing usable next-hop entry permits fallback to managed flooding. Intermediate CLIENT/ALL nodes can forward within the hop budget without a complete global NodeDB. Known destination and endpoint-key provisioning do not require provisioning every participant at each transit node.
Assessment method
Primary documentation and selected firmware review; no runtime experiment
Source context
Official discovery documentation and pinned forwarding code
Outstanding qualification
This uses the selected ordinary CLIENT/ALL forwarding case, not the separate F16 KNOWN_ONLY administrative witness. The destination identifier and trusted endpoint key are supplied. Hop limits, duplicate suppression, radio loss and congestion constrain reachability; flooding does not establish global capacity or arbitrary name discovery. No radio experiment was run.
Public sources
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round495.html
- round495-sources.json