The height to query the quorum state for
An array of public keys identifying service nodes which are being tested for the queried height.
An array of public keys identifying service nodes which are responsible for voting on the queried height.
The height to query the staking requirement for
The staking requirement in Beldex atomic units for the queried height
The public key identifying the queried service node
An array of service node public keys in strings that you wish to query metadata for. If an empty array is given, this RPC command returns all service nodes it knows about.
The array of metadata for the queried service node(s)
The queried service node’s identifying public key
The height at which the registration transaction arrived on the blockchain
The last block height this service node received a reward. Rewards are sent to service nodes whom have been waiting longest since their last reward and are then sent to the back of the queue.
The position in the queue to receive a reward for the service nodes grouped in the last_reward_block_height.
Unix epoch timestamp of the last time this daemon has received a ping from the queried service node.
An array consisting of all the addresses that have contributed to the queried service node.
The amount of Beldex in atomic units the contributor has staked.
The amount of Beldex in atomic units the contributor has reserved and must fulfill to completely contribute their part to the service node. Amount is equal to reserved once the contributor has fully contributed their part.
The Beldex address that funds must come from to fulfill the contribution requirement.
The total Beldex currently contributed going towards the staking requirement.
The total Beldex that has been reserved by all contributors. The remaining Beldex is open for other contributors to increase their stake towards the service node.
The operator cut expressed as a value from 0 -> STAKING_PORTIONS (defined in beldex/src/cryptonote_config.h) which is the fee taken from the service node reward and given to the operator address before rewards are distributed to the contributors.
The wallet address which is the primary owner of the service node and also the address which the operator cut is sent to.