Back to matrix

D04-RT: Yes

Rationale

The Reticulum 1.5.5 API generates encryption/signing keys through RNS.Identity. Official examples construct a new identity and a SINGLE destination inside the application, then use that destination for communication. Identity and destination creation do not require another serial-interface configuration or host network address. Credit this over the selected already authorized serial transport.

Assessment method

Documentary API and selected-profile analysis; no new network execution

Source context

Official API/specification and implementation documentation retrieved 2026-10-15; retained source digests

Outstanding qualification

Serial-device permission, IFAC credentials and initial transport setup remain prerequisites. This does not claim simultaneous exclusive ownership of one serial device by unrelated processes, unlimited announces, or exemption from resource limits. The selected no-local-TCP-sharing profile is unchanged; the evidence concerns identities within an authorized runtime, not a newly introduced sharing daemon.

Public sources

• https://reticulum.network/manual/reference.html
• https://reticulum.network/manual/examples.html

Editorial evidence references

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

• round239-sources.json