Response expected from a ServerInfoRequest.
If true, this server is amendment blocked. If the server is not amendment blocked, the response omits this field.
The version number of the running rippled version.
Information on the most recently closed ledger that has not been
validated by consensus. If the most recently validated ledger is
available, the response omits this field and includes
validated_ledger instead. The member fields are the same as the.
Range expression indicating the sequence numbers of the ledger versions the local rippled has in its database.
On an admin request, returns the hostname of the server running the rippled instance; otherwise, returns a single RFC-1751 word based on the node public key.
Amount of time spent waiting for I/O operations, in milliseconds. If this number is not very, very low, then the rippled server is probably having serious load issues.
The number of times (since starting up) that this server has had over 250 transactions waiting to be processed at once. A large number here may mean that your server is unable to handle the transaction load of the XRP Ledger network.
Information about the last time the server closed a ledger, including the amount of time it took to reach a consensus and the number of trusted validators participating.
The amount of time it took to reach a consensus on the most recently validated ledger version, in seconds.
How many trusted validators the server considered (including itself, if configured as a validator) in the consensus process for the most recently validated ledger version.
(Admin only) Detailed information about the current load state of the server.
(Admin only) Information about the rate of different types of jobs the server is doing and how much time it spends on each.
(Admin only) The number of threads in the server's main job pool.
The load-scaled open ledger transaction cost the server is currently enforcing, as a multiplier on the base transaction cost. For example, at 1000 load factor and a reference transaction cost of 10 drops of XRP, the load-scaled transaction cost is 10,000 drops (0.01 XRP). The load factor is determined by the highest of the individual server's load factor, the cluster's load factor, the open ledger cost and the overall network's load factor.
Current multiplier to the transaction cost based on load to servers in this cluster.
The current multiplier to the transaction cost that a transaction must pay to get into the open ledger.
The current multiplier to the transaction cost that a transaction must pay to get into the queue, if the queue is full.
Current multiplier to the transaction cost based on load to this server.
Current multiplier to the transaction cost being used by the rest of the network.
The load factor the server is enforcing, not including the open ledger cost.
The network id of the server.
The number of peer connections which were severed.
The number of peer connections which were severed due to excess resource consumption.
How many other rippled servers this one is currently connected to.
What Websocket/RPC ports rippled is listening on. This allows crawlers to build a richer topology without needing to port-scan nodes. For non-admin users (including peers), info about admin ports is excluded.
Public key used to verify this server for peer-to-peer communications. This node key pair is automatically generated by the server the first time it starts up. (If deleted, the server can create a new pair of Keys.).
Public key used by this node to sign ledger validations.
A string indicating to what extent the server is participating in the network.
The number of consecutive microseconds the server has been in the current state.
A map of various server states with information about the time the server spends in each. This can be useful for tracking the long-term health of your server's connectivity to the network.
The current time in UTC, according to the server's clock.
Number of consecutive seconds that the server has been operational.
Information about the most recent fully-validated ledger.
The time since the ledger was closed, in seconds.
Base fee, in XRP. This may be represented in scientific notation. Such as 1e-05 for 0.00005.
Unique hash for the ledger, as hexadecimal.
Minimum amount of XRP (not drops) necessary for every account to. Keep in reserve .
Amount of XRP (not drops) added to the account reserve for each object an account owns in the ledger.
The ledger index of the latest validated ledger.
Minimum number of trusted validations required to validate a ledger version. Some circumstances may cause the server to require more validations.
Either the human readable time, in UTC, when the current validator list will expire, the string unknown if the server has yet to load a published validator list or the string never if the server uses a static validator list.
Generated using TypeDoc