Made the following modifications related to the get_activated_protocol_features API call:
Corrected documentation that indicated a wrong format of the POST json payload needed for this call.
When the search_by_block num was used, the range of values to act was always empty due to a bug on the lower_bound_value used for both upper_bound and lower_bound.
Added some extra checks on the integration test plugin_http_api_test to take into account the data returned by the api call.
Made the following modifications related to the get_activated_protocol_features API call:
Change Description
Change Type
Select ONE:
Testing Changes
Select ANY that apply:
Consensus Changes
API Changes
Documentation Additions