G02-NS: No
Rationale
NIP-01 lets a publisher reconnect to known relays and submit the same signed event from a new access. Readers still request the event from those relays; no route or location mapping to the publisher is updated for external delivery. Event availability and the publisher's WebSocket connection change, but this is the initiating-client reconnection case explicitly excluded by G02. Basic Nostr does not supply a destination-attachment update mechanism at this service boundary.
Assessment method
Primary documentation and pinned source review; no runtime experiment
Source context
NIP-01 client/relay boundary and G02 destination-update requirement
Outstanding qualification
C01 remains Yes for retrieval of the unchanged event ID after republication. That content-level recovery does not establish scoped location updates, and absence of a global announcement alone is insufficient. This No does not claim that Nostr floods location changes or lacks useful mobility for its users. The selected composition has known relays and NIP-01; no relay-discovery/migration extension or separate IP host-mobility arrangement is credited. Relay acceptance, retention and connectivity still govern content availability. No runtime experiment.
Public sources
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round487.html#G02
- round537.html
- round565.html
- round565-sources.json