Participant Relationship Protocol

Back to matrix

G01-MT: Pending

Rationale

The ordinary CLIENT profile has a bounded packet reachability envelope, not a demonstrated requirement for a global destination catalog. HOP_MAX is seven; the source transmission does not consume a relay decrement, and each subsequent ordinary relay sends with one less remaining hop. A destination can receive the zero-budget transmission, so the bound is eight radio edges, not an assertion of seven physical links. Radio serialization clamps an oversized hop value. Zero-cost favorite-router forwarding requires other roles and cannot be imported into this profile. The zero-budget exhaustHops branch appears to be an exception, but its controlling TrafficManagementModule flag is initialized/reset false and never enabled in this pinned implementation. Opaque forwarding also decrements. A graph whose diameter exceeds eight necessarily contains pairs unreachable by this forwarding mechanism; a star has diameter two and is not ruled out by the hop counter alone. Neither fact supplies a worldwide radio topology. Published range records are observations, not universal physical range ceilings; multiplying one by eight cannot prove global operation impossible. G01 stays Pending until a complete geographic link/state construction is established, or a profile-wide impossibility proof is available. The independent 32-bit G05 namespace contradiction remains unchanged.

Assessment method

Pinned forwarding/radio/traffic-management source trace and reachability-bound analysis; no firmware or RF execution

Source context

Meshtastic 8e6a88d: MeshTypes, Router, NextHopRouter, RadioInterface and TrafficManagementModule

Outstanding qualification

For ordinary CLIENT forwarding, HOP_MAX=7 permits at most seven relays after the originating radio transmission: at most eight radio edges for one packet, absent an added gateway/reoriginator. Router preservation is unavailable to this role; opaque forwarding decrements too. The apparent exhaustHops zero-budget relay exception is inactive in the pinned TrafficManagementModule, whose flag is initialized/reset false and never enabled. Supply a connected geographic radio construction within this diameter, unique destination identities, compatible radio settings and all-role state inventory. A short-diameter abstract graph is not a global RF deployment; an observed range record is not a physical upper bound. See round142.html.

Public sources

Editorial evidence references

The following identifiers refer to research records not included in this public package; they are not public links.