This is an urgent hotfix release
The bug itself actually goes back to 2020 and has to do with misbehavior in the stacks-node's mempool syncing logic which causes some nodes to return improper messages in response to RPC calls used by normal mempool syncing.
Stacks-nodes who invoke that RPC call have misbehaving logic which causes their networking to become unresponsive, which hasn't been an issue until there was a lot more data getting run through some recent blocks.
A Deeper post-mortem will be released after full resolution as well.
This release is compatible with chainstate directories from 3.x.x.x.x.
The version of stacks-core compatible with this release is 3.1.0.0.11, available at: https://github.com/stacks-network/stacks-core/releases/tag/3.1.0.0.11.
Added
- Hotfix for p2p stack misbehavior in mempool syncing conditions