F29-NS: Yes
Rationale
NIP-01 defines an event ID as a digest of the serialized event and a REQ ids filter. Within the selected configured relay pool, a client can query the same exact event ID at multiple relays and accept a matching returned copy without knowing beforehand which relay stores it. The event reference, rather than a fixed origin-server address, selects the requested object.
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
Bounded application-layer retrieval from configured candidate relays: the client still opens WebSocket connections to those relays, which are explicit service dependencies. This is not global relay discovery, inter-relay request forwarding or guaranteed availability. The credited behavior does not require choosing one specific supplier in advance, but it does require knowing a relay pool and the event ID. Limit the witness to retained regular events queried by exact ID; verify the returned event digest/signature. Replaceable-event latest-version discovery and external files linked in content are not inferred.
Public sources
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