pub struct PendingInboundPair {
pub peer_handle: String,
pub peer_did: String,
pub peer_card: Value,
pub peer_relay_url: String,
pub peer_slot_id: String,
pub peer_slot_token: String,
pub peer_endpoints: Vec<Endpoint>,
pub event_id: String,
pub event_timestamp: String,
pub received_at: String,
}Expand description
One pending-inbound pair-request awaiting receiver-side wire add.
Fields§
§peer_handle: StringBare handle (no @<relay> suffix). Matches the on-disk key.
peer_did: StringFull DID of the peer (e.g. did:wire:alice-abc12345).
peer_card: ValuePeer’s signed agent-card from the pair_drop body. Already signature-verified at write time.
peer_relay_url: StringPeer’s relay URL — where we’d POST our ack and future events.
peer_slot_id: StringPeer’s slot_id on their relay — write target for ack + sends.
peer_slot_token: StringPeer’s slot_token — they shipped it in the drop so we can write
back. Holding this without acting on it is intentional: capability
only flows when operator runs wire add to accept.
peer_endpoints: Vec<Endpoint>v0.5.17: full set of endpoints the peer advertised (federation +
optional local). When the operator accepts via wire pair-accept,
every endpoint here gets pinned into relay_state via
endpoints::pin_peer_endpoints. Absent on records written by
v0.5.16-and-earlier code paths; downstream code synthesizes a
single federation entry from the legacy fields in that case.
event_id: StringOriginal pair_drop event_id (SHA-256 over canonical body). Used to dedupe repeated drops from the same key.
event_timestamp: StringRFC3339 timestamp from the pair_drop event itself.
received_at: StringRFC3339 timestamp of when we wrote this pending record.
Trait Implementations§
Source§impl Clone for PendingInboundPair
impl Clone for PendingInboundPair
Source§fn clone(&self) -> PendingInboundPair
fn clone(&self) -> PendingInboundPair
1.0.0 (const: unstable) · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more