Is there any reason for the removal of all these fields? A lot of them were extremely useful to determine the health of a node, as well as other monitoring possibilies.
These 3 properties were used for calculating the consensus, but with the new BFT rules, these are no longer needed, and they donât exist it the code anymore.
âloadedâ: true,
This property was always true now after changing the initialization order, so no longer needed.
This transaction count was removed because to get the total count, query was too slow.
Also, it is not so useful property for the blockchain client to have them.
However, in the coming release, we are adding the number of unconfirmed transaction, which is necessary for the client.
I believe before going to the mainnet, we will introduce a way to check the status easily.
The answer depends on how we define the health of the node, but in general term, if you have
connected peers (which you can see from the /api/peers
height is moving
It should be properly moving forward with the chain.
For the network health, chainMaxHeightFinalized should be also moving every few blocks.