Skip to main content

Module peer

Module peer 

Source
Expand description

Explicitly started URMA peer transport. Noise authenticates the remote transport identity; packages still need independent Engine admission. There are no built-in seeds, wallet keys or implicit listeners. Names in explicitly dialed /dns* addresses resolve through the system resolver.

Re-exports§

pub use crate::peer_live::PeerSource;
pub use crate::peer_live::SyncPeers;
pub use crate::peer_parent::OverlayCommitSource;
pub use crate::peer_transport::Dns;
pub use crate::peer_transport::DnsMode;

Structs§

OverlayCommitSource
Tries one window of the current overlay peers (configured, then live) per fetch; successive fetches move to the next window, so every peer is visited. verify_parent binds bytes to the TXID; a peer whose bytes fail it only lets the next peer be tried and is disconnected so it keeps no slot. Engine verification is final.
PeerNetwork
Owns one network thread and one bounded archive-reader thread. Drop requests shutdown and joins both. An archive operation already running is not forcibly interrupted. Source handles do not keep the network alive after this owner.

Enums§

Dns
Whether this swarm can resolve names, and why not.
DnsMode
How the overlay resolves names. Refuse stands in for an unreadable system configuration (tests inject it); it is never a fallback resolver.