Get network data
GET/api/v2/network/data
Get data regarding the nodes of the network
Responses
- 200
- 500
- default
A successful response.
- application/json
- Schema
- Example (from schema)
Schema
nodeData object
Summary of information with respect to nodes on the Vega network.
ersatzNodes object
Details on the set of ersatz (standby) nodes in the network.
IDs of nodes that were demoted into this node set at the start of the epoch.
Number of nodes in the node set that had a performance score of 0 at the end of the last epoch.
Total number of nodes allowed in the node set.
IDs of nodes that were promoted into this node set at the start of the epoch.
Total number of nodes in the node set.
Total number of nodes that had a performance score of 0 at the end of the last epoch.
pendingNodes object
Details on the set of pending nodes in the network.
IDs of nodes that were demoted into this node set at the start of the epoch.
Number of nodes in the node set that had a performance score of 0 at the end of the last epoch.
Total number of nodes allowed in the node set.
IDs of nodes that were promoted into this node set at the start of the epoch.
Total number of nodes in the node set.
Total staked amount across all nodes. This field is an unsigned integer scaled to the asset's decimal places.
tendermintNodes object
Details on the set of consensus nodes in the network.
IDs of nodes that were demoted into this node set at the start of the epoch.
Number of nodes in the node set that had a performance score of 0 at the end of the last epoch.
Total number of nodes allowed in the node set.
IDs of nodes that were promoted into this node set at the start of the epoch.
Total number of nodes in the node set.
Total number of nodes across all node sets.
Total uptime for all epochs across all nodes.
{
"nodeData": {
"ersatzNodes": {
"demoted": [
"string"
],
"inactive": 0,
"maximum": 0,
"promoted": [
"string"
],
"total": 0
},
"inactiveNodes": 0,
"pendingNodes": {
"demoted": [
"string"
],
"inactive": 0,
"maximum": 0,
"promoted": [
"string"
],
"total": 0
},
"stakedTotal": "string",
"tendermintNodes": {
"demoted": [
"string"
],
"inactive": 0,
"maximum": 0,
"promoted": [
"string"
],
"total": 0
},
"totalNodes": 0,
"uptime": 0
}
}
An internal server error
- application/json
- Schema
- Example (from schema)
Schema
- Array [
- If no scheme is provided,
https
is assumed. - An HTTP GET on the URL must yield a [google.protobuf.Type][] value in binary format, or produce an error.
- Applications are allowed to cache lookup results based on the URL, or have them precompiled into a binary to avoid any lookup. Therefore, binary compatibility needs to be preserved on changes to types. (Use versioned type names to manage breaking changes.)
- ]
details object[]
A URL/resource name that uniquely identifies the type of the serialized
protocol buffer message. This string must contain at least
one "/" character. The last segment of the URL's path must represent
the fully qualified name of the type (as in
path/google.protobuf.Duration
). The name should be in a canonical form
(e.g., leading "." is not accepted).
In practice, teams usually precompile into the binary all types that they
expect it to use in the context of Any. However, for URLs which use the
scheme http
, https
, or no scheme, one can optionally set up a type
server that maps type URLs to message definitions as follows:
Note: this functionality is not currently available in the official protobuf release, and it is not used for type URLs beginning with type.googleapis.com.
Schemes other than http
, https
(or the empty scheme) might be
used with implementation specific semantics.
{
"code": 0,
"details": [
{
"@type": "string"
}
],
"message": "string"
}
An unexpected error response.
- application/json
- Schema
- Example (from schema)
Schema
- Array [
- If no scheme is provided,
https
is assumed. - An HTTP GET on the URL must yield a [google.protobuf.Type][] value in binary format, or produce an error.
- Applications are allowed to cache lookup results based on the URL, or have them precompiled into a binary to avoid any lookup. Therefore, binary compatibility needs to be preserved on changes to types. (Use versioned type names to manage breaking changes.)
- ]
details object[]
A URL/resource name that uniquely identifies the type of the serialized
protocol buffer message. This string must contain at least
one "/" character. The last segment of the URL's path must represent
the fully qualified name of the type (as in
path/google.protobuf.Duration
). The name should be in a canonical form
(e.g., leading "." is not accepted).
In practice, teams usually precompile into the binary all types that they
expect it to use in the context of Any. However, for URLs which use the
scheme http
, https
, or no scheme, one can optionally set up a type
server that maps type URLs to message definitions as follows:
Note: this functionality is not currently available in the official protobuf release, and it is not used for type URLs beginning with type.googleapis.com.
Schemes other than http
, https
(or the empty scheme) might be
used with implementation specific semantics.
{
"code": 0,
"details": [
{
"@type": "string"
}
],
"message": "string"
}