D04-YG: No
Rationale
The documented ordinary IPv6 application path uses a TUN interface. PrivateKey controls the node key, while IfName selects that interface; disabling it produces router-only mode. The official FAQ explicitly says that this mode cannot originate or receive application traffic through the Yggdrasil IPv6 address. Locally generating another key therefore does not by itself supply an additional usable user identity over the already configured IPv6 application endpoint; interface/address provisioning remains involved.
Assessment method
Documentary selected-stack classification; no new network execution
Source context
Official API, protocol and configuration documentation; retained origin bytes or explicitly labelled web extractions, 2026-10-15
Outstanding qualification
No is scoped to the selected ordinary IPv6/UDP application path, not key generation or external-authority independence. A separate userspace IPv6 frontend or identity-multiplexing API could change this boundary but is not credited without an explicit supported profile. Preconfiguring an address for each identity is precisely the per-identity provisioning D04 excludes. Existing delegated-interface operation in D01 remains a separate question.
Public sources
- https://yggdrasil-network.github.io/configurationref.html
- https://yggdrasil-network.github.io/faq.html
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round241-sources.json