Module safe_network::messaging::node [−][src]
Expand description
Node to node messages
Structs
One signed failure for a DKG round by a given PublicKey
Dkg failure info for a round
Unique identifier of a DKG session.
The information about elder candidates in a DKG round.
Request to join a section as relocated from another section
Request to join a section
Signature created when a quorum of the section elders has agreed on something.
Container for storing information about other sections in the network.
Information about a member of our section.
Information on our sibling section
Network p2p peer identity.
When a node knows another p2p_node as a Peer it’s implicitly connected to it. This is separate
from being connected at the network layer, which currently is handled by quic-p2p.
Section-source message without signature and proof.
Container that acts as a map whose keys are prefixes.
Details of a relocation: which node to relocate, where to relocate it to and what age it should get once relocated.
Details of a node relocation and new signed name
Relocate node of
Joining peer’s proof of resolvement of given resource proofing challenge.
Routing message sent over the network.
Container for storing information about a section. All information about a section
Container for storing information about members of our section.
A value together with the signature that it was agreed on by the majority of the section elders.
Single share of KeyedSig.
Aggregator for signature shares for arbitrary payloads.
RoutingMsg with Variant::Relocate in a convenient wrapper.
Enums
Error returned from SignatureAggregator::add.
Response to a request to join a section as relocated
Reason of a join request being rejected
Response to a request to join a section
Node’s current section membership state
Query originating at a node
Reward query that is sent between sections.
Cmds related to the running of a node.
A step in the Propose-Broadcast-Aggregate-Execute workflow. A proposal about the state of the network This can be a result of seeing a node come online, go offline, changes to section info etc. Anything where we need section authority before action can be taken
Source authority of a message. Src of message and authority to send it. Authority is validated by the signature. Messages do not need to sign this field as it is all verifiable (i.e. if the sig validates agains the pub key and we know th epub key then we are good. If the proof is not recognised we ask for a longer chain that can be recognised). Therefore we don’t need to sign this field.
Message variant