This patch release contains fixes for handling forks in state_history_plugin. All users of state_history_plugin running 3.2.1 or 3.2.2 are highly recommended to update to 3.2.3. Downstream consumers of state history data may have been affected by this defect.

state_history_plugin log files remain correct (not corrupt) for affected nodeos versions. However, in 3.2.1 and 3.2.2 there is a possibility when nodeos switches to a new fork, blocks from this new fork will not be sent to existing state_history_plugin connections. The side effects of this will be dependent on the downstream application that is consuming from state_history_plugin, but most likely will result in the downstream application consuming incorrect or missing data for a block because the downstream application will be unaware that a fork has occurred. Users that have populated downstream applications from 3.2.1 or 3.2.2 should repopulate downstream applications with 3.2.3 starting from a block prior to their upgrade to 3.2.1 or 3.2.2.