Crate zebra_network

Networking code for Zebra.

Network Protocol Design

The Zcash network protocol is inherited from Bitcoin, which uses a stateful network protocol in which messages can arrive in any order (even before a handshake is complete!). The same Bitcoin message may be a request or a response depending on context.

Achieving Concurrency

This crate translates the legacy Zcash network protocol into a stateless, request-response oriented protocol defined by the Request and Response enums. zebra-network completely encapsulates all peer handling code behind a single tower::Service representing “the network”, which load-balances outbound Requests over available peers.

Unlike the underlying legacy network protocol, Zebra’s PeerSet tower::Service guarantees that each Request future will resolve to the correct Response, rather than an unrelated Response message.

Each peer connection is handled by a distinct [peer::Connection] task. The Zcash network protocol is bidirectional, so Zebra interprets incoming Zcash messages as either:

• Responses to previously sent outbound Requests, or
• inbound Requests to an internal tower::Service representing “this node”.

All connection state is isolated to individual peers, so this design is structurally immune to the recent ping attack.

Connection Pool

Because tower::Services provide backpressure information, we can dynamically manage the size of the connection pool according to inbound and outbound demand. The inbound service can shed load when it is not ready for requests, causing those peer connections to close, and the outbound service can connect to additional peers when it is overloaded.

zebra-network Structure

[zebra-network::init] is the main entry point for zebra-network. It uses the following services, tasks, and endpoints:

Low-Level Network Connections

Inbound Zcash Listener Task:

• accepts inbound connections on the listener port
• initiates Zcash [peer::Handshake]s, which creates [peer::Connection] tasks for each inbound connection

Outbound Zcash Connector Service:

• initiates outbound connections to peer addresses
• initiates Zcash [peer::Handshake]s, which creates [peer::Connection] tasks for each outbound connection

Zebra uses direct TCP connections to share blocks and mempool transactions with other peers.

The [isolated] APIs provide anonymised TCP and Tor connections to individual peers. These isolated connections can be used to send user-generated transactions anonymously. Tor connections are currently disabled until arti-client’s dependency x25519-dalek v1.2.0 is updated to a higher version. See #5492.

Individual Peer Connections

Each new peer connection spawns the following tasks:

peer::Client Service:

• provides an interface for outbound requests to an individual peer
  • accepts Requests assigned to this peer by the PeerSet
  • sends each request to the peer as Zcash Message
  • waits for the inbound response Message from the peer, and returns it as a Response

[peer::Connection] Service:

• manages connection state: awaiting a request, or handling an inbound or outbound response
• provides an interface for inbound requests from an individual peer
  • accepts inbound Zcash Messages from this peer
  • handles each message as a Request to the inbound service
  • sends the Response to the peer as Zcash Messages
• drops peer connections if the inbound request queue is overloaded

Since the Zcash network protocol is bidirectional, inbound and outbound connections are handled using the same logic.

Connection Pool

PeerSet Network Service:

• provides an interface for other services and tasks running within this node to make requests to remote peers (“the rest of the network”)
  • accepts Requests from the local node
  • sends each request to a peer::Client using randomised load-balancing
  • returns the Response from the peer::Client

Inbound Network Service:

• provides an interface for remote peers to request data held by this node
  • accepts inbound Zcash Requests from [peer::Connection]s
  • handles each message as a Request to the local node
  • sends the Response to the [peer::Connection]

Note: the inbound service is implemented by the [zebra-network::init] caller.

Peer Inventory Service:

• tracks gossiped inv advertisements for each peer
• tracks missing inventory for each peer
• used by the PeerSet to route block and transaction requests to peers that have the requested data

Peer Discovery

AddressBook Service:

• maintains a list of peer addresses and associated connection attempt metadata
• address book metadata is used to prioritise peer connection attempts

Initial Seed Peer Task:

• initiates new outbound peer connections to seed peers, resolving them via DNS if required
• adds seed peer addresses to the AddressBook

Peer Crawler Task:

• discovers new peer addresses by sending Addr requests to connected peers
• initiates new outbound peer connections in response to application demand

Re-exports

• pub use crate::address_book_peers::AddressBookPeers;

Modules

• address_book_peers
  A AddressBookPeers trait for getting the MetaAddr of recently live peers.
• constants
  Definitions of Zebra network constants, including:
• types
  Types used in the definition of Request, Response, and VersionMessage.

Structs

• AddressBook
  A database of peer listener addresses, their advertised services, and information on when they were last seen.
• Client
  The “client” duplex half of a peer connection.
• Config
  Configuration for networking code.
• ConnectionInfo
  The metadata for a peer connection.
• RetryLimit
  A very basic retry policy with a limited number of retry attempts.
• SharedPeerError
  A wrapper around Arc<PeerError> that implements Error.
• Version
  A protocol version number.
• VersionMessage
  A version message.

Enums

• ConnectedAddr
  The peer address that we are handshaking with.
• HandshakeError
  An error during a handshake with a remote peer.
• InventoryResponse
  A generic peer inventory response status.
• PeerAddrState
  Peer connection state, based on our interactions with the peer.
• PeerError
  An error related to peer connection handling.
• Request
  A network request, represented in internal format.
• Response
  A response to a network request, represented in internal format.

Functions

• connect_isolated
  Creates a Zcash peer connection using the provided data stream. This connection is completely isolated from all other node state.
• connect_isolated_tcp_direct
  Creates a direct TCP Zcash peer connection to addr. This connection is completely isolated from all other node state.
• connect_isolated_tcp_direct_with_inbound
  Creates an isolated Zcash peer connection using the provided data stream. This function is for testing purposes only.
• connect_isolated_with_inbound
  Creates an isolated Zcash peer connection using the provided data stream. This function is for testing purposes only.
• init
  Initialize a peer set, using a network config, inbound_service, and latest_chain_tip.

Type Definitions

• BoxError
  Type alias to make working with tower traits easier.