Network_status_response (rosetta_models.Rosetta_models.Network_status

type t = {

current_block_identifier : Block_identifier.t;

current_block_timestamp : int64;

genesis_block_identifier : Block_identifier.t;

oldest_block_identifier : Block_identifier.t option;

sync_status : Sync_status.t option;

peers : Peer.t list;

}

val to_yojson : t -> Yojson.Safe.t

val of_yojson : Yojson.Safe.t -> t Ppx_deriving_yojson_runtime.error_or

val _ : Yojson.Safe.t -> t Ppx_deriving_yojson_runtime.error_or

val pp : 
  Ppx_deriving_runtime.Format.formatter ->
  t ->
  Ppx_deriving_runtime.unit

val show : t -> Ppx_deriving_runtime.string

val equal : t -> t -> Ppx_deriving_runtime.bool

val create : Block_identifier.t -> int64 -> Block_identifier.t -> t

NetworkStatusResponse contains basic information about the node's view of a blockchain network. It is assumed that any BlockIdentifier.Index less than or equal to CurrentBlockIdentifier.Index can be queried. If a Rosetta implementation prunes historical state, it should populate the optional `oldest_block_identifier` field with the oldest block available to query. If this is not populated, it is assumed that the `genesis_block_identifier` is the oldest queryable block. If a Rosetta implementation performs some pre-sync before it is possible to query blocks, sync_status should be populated so that clients can still monitor healthiness. Without this field, it may appear that the implementation is stuck syncing and needs to be terminated.