Table of Contents

Enum PeersInfo.Types.Peer.Types.CatchupStatus

Namespace
Concordium.Grpc.V2
Assembly
Concordium.Sdk.dll
public enum PeersInfo.Types.Peer.Types.CatchupStatus

Fields

[OriginalName("CATCHINGUP")] Catchingup = 2

The node is currently catching up by requesting blocks from this peer. There will be at most one peer with this status at a time. Once the peer has responded to the request, its status will be changed to:

  • 'UPTODATE' if the peer has no more data that is not known to us
  • 'PENDING' if the node has more data that is unknown to us.
[OriginalName("PENDING")] Pending = 1

The peer might have some data unknown to us. A peer can be in this state either because it sent a message that refers to data unknown to us, or before we have established a baseline with it. The latter happens during node startup, as well as upon protocol updates until the initial catchup handshake completes.

[OriginalName("UPTODATE")] Uptodate = 0

The peer does not have any data unknown to us. If we receive a message from the peer that refers to unknown data (e.g., an unknown block) the peer is marked as pending.