pub struct ChiaPeersAddResult {
pub added: bool,
pub ip: String,
pub port: u16,
pub corroboration_bypassed: bool,
pub notice: String,
}Expand description
control.chiaPeers.add — the acknowledgement, including the cost that was paid.
Fields§
§added: boolAlways true on success (idempotent — re-adding a known peer succeeds and un-bans it).
ip: StringThe peer’s IP address as stored, in the canonical form defined by
crate::params::canonical_peer_ip.
port: u16The port the entry was stored at.
corroboration_bypassed: boolWhether this peer is NOW believed without corroboration — the RESULTING trust state, not a restatement of what was asked for.
true in the ordinary case, and a conforming node MUST report false where the entry did
not end up trusted, however that came about (an upsert that touches other columns and
leaves the trusted flag alone is how it happens in practice). Reported honestly, this is
the only way an operator learns that the node they believe they configured is still subject
to corroboration; reported as a constant, it is a claim about custody-grade authority that
nothing checks.
notice: StringThe human-readable warning the node authored for this call, to be rendered VERBATIM to the person who made it.
This is the field a client quotes instead of restating the cost locally and drifting from the node’s wording. It MUST be non-empty and MUST name the corroboration bypass; a client MUST NOT paraphrase, truncate or suppress it.
Trait Implementations§
Source§impl Clone for ChiaPeersAddResult
impl Clone for ChiaPeersAddResult
Source§fn clone(&self) -> ChiaPeersAddResult
fn clone(&self) -> ChiaPeersAddResult
1.0.0 (const: unstable) · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more