G02-GN: Yes
Rationale
After a destination changes its UDP attachment while retaining its peer identity, supplied usable contacts reattach it to the mesh. CADET publishes its current HELLO under the peer-derived DHT key with route recording; interested peers search that key and use returned GET/PUT paths as connection candidates. R5N forwards operations through selected neighbors and replicas rather than requiring an updated location entry at every peer. Remote discovery and path state change without a network-wide per-destination update requirement.
Assessment method
Primary documentation and pinned source review; no runtime experiment
Source context
GNUnet 0.20.0 CADET DHT publication and R5N path discovery
Outstanding qualification
Use the existing C01 witness with admitted contacts, connected neighbors and already-routed private-IP access. DEMULTIPLEX_EVERYWHERE permits caching along traversed paths; it does not mean a broadcast to every peer. Repeated publications, searches and changing replica placement can reach additional participants. Discovery is probabilistic and may fail or be delayed; stale paths must be replaced. No fixed recipient count, global-capacity bound, automatic arbitrary-address discovery or seamless channel migration is inferred. The selected 0.20.x composition remains documentary, not an integrated runtime result.
Public sources
- https://docs.gnunet.org/v0.20.x/developers/dht/dht.html
- https://docs.gnunet.org/v0.20.x/developers/cadet/cadet.html
- https://ftpmirror.gnu.org/gnunet/gnunet-0.20.0.tar.gz
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round558.html
- round558-sources.json