#[non_exhaustive]pub struct FederatedAttributes {
pub stamp_required: bool,
pub peer_class: FederatedPeerClass,
pub peer_fingerprint: String,
pub peer_box_id: Option<String>,
pub pairing_id: String,
pub peer_name: String,
pub origin_principal: Option<Principal>,
pub project: Option<FederatedProject>,
pub remote_claim: Option<RemoteClaim>,
}Expand description
Facts from the local pairing roster. Fixed for the scope’s epoch.
Fields (Non-exhaustive)§
This struct is marked as non-exhaustive
Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.stamp_required: boolRequire a federated stamp instead of falling back to a legacy bind. This daemon instruction is removed from provider-facing stamps.
peer_class: FederatedPeerClass§peer_fingerprint: String§peer_box_id: Option<String>Stable paired computer machine id from the pairing roster, absent for
phones and simulators. Unlike peer_fingerprint, it survives a re-key,
so receivers comparing records of which computer hosts a resource use
this id.
pairing_id: String§peer_name: String§origin_principal: Option<Principal>The principal the sending computer’s daemon stamped on the route that
opened this call, carried by the pairing module. It sits beside the claim
because a module-to-module call carries no claim. Only reserved names
a launch-verified module.
project: Option<FederatedProject>Portable project and root keys from the sending session’s scope stamp.
remote_claim: Option<RemoteClaim>Implementations§
Source§impl FederatedAttributes
impl FederatedAttributes
Sourcepub fn same_identity(&self, other: &Self) -> bool
pub fn same_identity(&self, other: &Self) -> bool
Compare the facts fixed for an epoch, ignoring only the remote claim’s
display names. Every other field counts, including any added later;
peer_name is a fixed pairing-roster fact, not a display name here.