Add Obsolete indicator to non-admin `feature` RPC
Summary
Obsolete indicator is only available in feature RPC response via vetoed, which is unavailable in non-admin mode. Another boolean field (e.g obsolete/retired) should be added to feature response to identify amendments that are marked as obsolete in the code.
Motivation
Non-admin feature RPC should show obsolete information.
See also #4730
Related, it's misleading that the feature command shows retired amendments as "enabled": false even though the functionality associated with them is always enabled. Previous ticket: #4014.
I think this issue would be solved with #4730
Related, it's misleading that the
featurecommand shows retired amendments as"enabled": falseeven though the functionality associated with them is always enabled. Previous ticket: #4014.
Without adding a new state, rippled can't tell the difference between a retired feature and an obsolete feature. All enabled really tells you is whether the ID of the amendment is in the ledger. A better solution might be to hide / expunge any obsolete amendments that are not "enabled".