dig-peer 0.2.0

The DIG Network peer client: DigPeer::connect(peer, tls) drives dig-nat's full direct→relay traversal ladder, exposes typed RPC over dig-rpc-protocol, seals directed calls end-to-end to the peer's captured BLS-G1 identity (§5.4) on top of mTLS, and disconnects cleanly. The client mirror of dig-rpc's server; distinct from ChiaPeer.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28

//! The [`DigPeer`](crate::DigPeer) connection lifecycle.
//!
//! A DigPeer moves through a small, explicit state machine so callers (and the crate itself) always
//! know whether an RPC may be issued. The transitions are deliberately minimal — dig-peer's job is to
//! be a thin, honest client, so the state is just enough to reject use-after-disconnect and to report
//! liveness, not a full reconnection engine (opportunistic re-dial is a documented follow-up).

/// The lifecycle state of a [`DigPeer`](crate::DigPeer) connection.
///
/// A freshly [`connect`](crate::DigPeer::connect)ed peer is [`Connected`](PeerState::Connected).
/// [`disconnect`](crate::DigPeer::disconnect) moves it to [`Closed`](PeerState::Closed) terminally;
/// any RPC attempted after that fails with [`DigPeerError::InvalidState`](crate::DigPeerError::InvalidState).
#[derive(Debug, Clone, Copy, PartialEq, Eq, Hash)]
#[non_exhaustive]
pub enum PeerState {
    /// The mTLS connection is established and RPCs may be issued.
    Connected,
    /// The connection was explicitly torn down; no further RPCs are possible. Terminal.
    Closed,
}

impl PeerState {
    /// Whether an RPC may be issued in this state.
    #[must_use]
    pub const fn is_usable(self) -> bool {
        matches!(self, PeerState::Connected)
    }
}