Back to matrix

F39-LP: Yes

Rationale

The application opens a stream using a Peer ID and protocol ID. BasicHost resolves the peer through its peerstore and network dialer. The selected QUIC transport supports distinct peers on the same machine using loopback, and peers on different machines, beneath that same stream interface.

Assessment method

Primary documentation, pinned source and explicit architectural composition; no runtime test

Source context

Peer-ID stream API and identity-derived virtual-address delivery

Outstanding qualification

Source-supported composition: provision the known peer addresses in the peerstore, including a usable local address for a co-resident peer. BasicHost.NewStream accepts only the logical peer reference; transport setup remains below that call. The v0.50.0 TestStreams fixture exercises QUIC loopback transport, but was inspected rather than executed here. No special shared-memory IPC, zero-copy, self-dial to the same peer identity or process-migration claim.

Public sources

Editorial evidence references

The following identifiers refer to research records not included in this public package; they are not public links.