pub fn installed_bootstrap_discovery_client() -> Option<DiscoveryClient>Expand description
The authenticated Discovery client this process’s own bootstrap installed, when bootstrap installed one.
Present after required-native bootstrap (checkpoint-backed resolver) and
after both DID-anchored arms — the remote-node network client
(KEM/PQ-bound, liveness-verified at install) and the same-node lazy local
client. None when no bootstrap ran, so callers fall back to their own
profile selection.
This — not the native-network profile — carries installed-bootstrap reach:
DID-anchored remote_node = true explicitly boots with
network_required = false, and the installed network client is the only
Discovery reach a remote node has. The client is authenticated per its
installing arm (pinned discovery key; remote-node additionally KEM/PQ-bound
and liveness-verified before install).