Skip to main content

Module actions

Module actions 

Source
Expand description

What the model can do as a devp2p dialler: choose this node’s Status, ask the peer for headers, bodies and pooled transactions, answer the peer’s requests, and disconnect.

The actions and the session events are the server’s (crate::server::devp2p::actions): after the handshake both ends of a devp2p session speak the same protocol. What differs is the Status event — a dialler may have to speak first — and the two events only a client has, devp2p_error and devp2p_disconnected.

Structs§

Devp2pClientProtocol

Statics§

ANNOUNCED_EVENT
BODIES_RECEIVED_EVENT
BODIES_REQUESTED_EVENT
DISCONNECTED_EVENT
ERROR_EVENT
HEADERS_RECEIVED_EVENT
HEADERS_REQUESTED_EVENT
POOLED_RECEIVED_EVENT
POOLED_REQUESTED_EVENT
REQUEST_TIMEOUT_EVENT
STATUS_EVENT