Current getchainstates RPC returns "normal" and "snapshot" fields which are not
ideal because it requires new "normal" and "snapshot" terms to be defined, and
the definitions are not really consistent with internal code. (In the RPC
interface, the "snapshot" chainstate becomes the "normal" chainstate after it
is validated, while in internal code there is no "normal chainstate" and the
"snapshot chainstate" is still called that temporarily after it is validated).
The current getchainstatees RPC is also awkward to use if you to want
information about the most-work chainstate because you have to look at the
"snapshot" field if it exists, and otherwise fall back to the "normal" field.
Fix these issues by having getchainstates just return a flat list of
chainstates ordered by work, and adding new chainstate "validated" field
alongside the existing "snapshot_blockhash" so it is explicit if a chainstate
was originally loaded from a snapshot, and whether the snapshot has been
validated.
{RPCResult::Type::STR_HEX,"snapshot_blockhash",/*optional=*/true,"the base block of the snapshot this chainstate is based on, if any"},
{RPCResult::Type::NUM,"coins_db_cache_bytes","size of the coinsdb cache"},
{RPCResult::Type::NUM,"coins_tip_cache_bytes","size of the coinstip cache"},
{RPCResult::Type::BOOL,"validated","whether the chainstate is fully validated. True if all blocks in the chainstate were validated, false if the chain is based on a snapshot and the snapshot has not yet been validated."},
};
staticRPCHelpMangetchainstates()
@ -2818,8 +2819,7 @@ return RPCHelpMan{
RPCResult{
RPCResult::Type::OBJ,"","",{
{RPCResult::Type::NUM,"headers","the number of headers seen so far"},
{RPCResult::Type::OBJ,"normal",/*optional=*/true,"fully validated chainstate containing blocks this node has validated starting from the genesis block",RPCHelpForChainstate},
{RPCResult::Type::OBJ,"snapshot",/*optional=*/true,"only present if an assumeutxo snapshot is loaded. Partially validated chainstate containing blocks this node has validated starting from the snapshot. After the snapshot is validated (when the 'normal' chainstate advances far enough to validate it), this chainstate will replace and become the 'normal' chainstate.",RPCHelpForChainstate},
{RPCResult::Type::ARR,"chainstates","list of the chainstates ordered by work, with the most-work (active) chainstate last",{{RPCResult::Type::OBJ,"","",RPCHelpForChainstate},}},