pub fn dial<S>(
target: &TransportConfig,
signer: S,
server_verifying_key: Option<VerifyingKey>,
token: Option<String>,
) -> Result<Arc<dyn RpcClient>>where
S: Signer + 'static,Expand description
Dial a resolved TransportConfig, returning a ready RPC client.
server_verifying_key is the destination’s response-verification key.
None does NOT disable signature verification — the response is still
cryptographically verified against the key embedded in its envelope; None
only declines to pin which identity that key must be. Network callers
should supply an independently resolved application response key. In
particular, iroh NodeId/EndpointId is only reach/path integrity and can
never fill this parameter.
For inproc:// there is no transport-level peer authentication (it is a
function call into a registry-resolved processor), so None is discouraged
on the inproc path: without it, a name-squatting registration could be dialed
without detection. Callers SHOULD pass the resolved service verifying key for
inproc. (The codegen wire-up will thread the resolver-supplied key through;
see #151(a) follow-up.)