Participant Relationship Protocol

Back to matrix

F22-MT: Yes

Rationale

The agreed channel configuration provides a shared discovery context. Independently keyed nodes broadcast NodeInfo there; the selected STRICT profile validates signed first-contact NodeInfo using its advertised public key and checks the node-number/key relation. NodeDB retains the separate keys and channel association. Thus received broadcasts yield independent participant candidates without a central membership signer. The channel PSK is a shared access/encryption credential, not a shared private identity. The full channel configuration, not its short packet hash alone, is the reference. This is bounded radio-mesh discovery, not arbitrary global alias lookup. A node number or display name alone is not a cryptographic identity; key confirmation for subsequent sensitive direct messages remains required by the selected profile.

Assessment method

Pinned firmware source analysis of channels, NodeInfo and signature policy; no radio execution

Source context

Meshtastic pinned Router.cpp: verifyFirstContactNodeInfo and checkXeddsaReceivePolicy

Outstanding qualification

On the pinned PKI-capable firmware with STRICT policy, configure three nodes on the same private channel and independent endpoint keys. Confirm two signed NodeInfo broadcasts populate distinct full-key records at the observer; reject invalid/unsigned broadcasts and key substitutions. Check channel association, collision handling, stale records and airtime throttling. No hardware experiment performed.

Public sources