C01-GN: Yes
Rationale
CADET addresses a remote peer by its public-key identity and service port, separately from its UDP locator and intermediate path. A bounded witness keeps that identity and service while replacing the destination's IPv4/UDP attachment with a usable configured contact. GNUnet TRANSPORT and CADET can establish authenticated low-level connectivity and a new path to the same peer; the caller does not substitute another peer identity.
Assessment method
Primary documentation and pinned source review; no runtime experiment
Source context
I2P LeaseSets and GNUnet CADET identity/path separation
Outstanding qualification
The selected GNUnet 0.20.0 witness assumes that usable HELLO/contact information for the replacement attachment is supplied, admitted and validated, and that the peer remains connected to the mesh. It does not infer automatic discovery of arbitrary new public addresses, NAT traversal or a GNS directory. New connections or channels are allowed; continuous old-channel delivery is not required. CADET source separates lost connection bindings from the destination tunnel and considers replacement paths, but this is not an executed mobility test or a guarantee that every candidate path is chosen. Final-peer policy and port availability must still permit communication; an F16-specific outgoing-only configuration is not evidence that any unsolicited incoming service is exposed.
Public sources
- 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.
- round534.html
- round534-sources.json