F30-RT: No
Rationale
The selected Reticulum 1.5.5 Link composition authenticates the live communication context, while Resource uses transfer hashes and a receipt proof derived from data and the resource hash. It does not attach an origin signature or independently provisioned trusted content reference to the Resource for verification after re-serving through another connection.
Assessment method
Primary specification and pinned code review; no runtime experiment
Source context
NIP-01 event queries and Reticulum 1.5.5 Resource evidence
Outstanding qualification
A hash advertised by the same supplier and a proof returned by the receiver are not independent origin evidence. Link.identify authenticates a peer in the Link, not a reusable object wrapper. An application could retain a digest obtained over an authenticated Link as a trusted reference, or use Identity signing to define signed objects; neither object-verification profile is selected here. LXMF is also excluded. This No does not deny transfer integrity, transport authentication, or the availability of generic signing primitives.
Public sources
- https://raw.githubusercontent.com/markqvist/Reticulum/1.5.5/RNS/Resource.py
- https://raw.githubusercontent.com/markqvist/Reticulum/1.5.5/RNS/Link.py
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round510.html
- round510-sources.json