A new version of the Bitcoin Core client has been released. According to the documentation, the code downgrades the status of nodes relaying invalid blocks to the network, and minor bugs have been fixed.
\n
\”Misbehaving peers\” in the log will be marked as \”restricted-access nodes\”. As a result, other clients are less likely to contact them. Preserving this status may now last more than a day depending on network load. The restriction is lifted after the node restarts.
\n
The update also fixes a notification bug that existed in the client from version 0.19. Users will again begin receiving notifications about transactions evicted from the mempool when they conflict with new blocks.
\n
Thirteen developers contributed to the update, reflected in a smaller number of entries in the changelog. In the previous version, there were 119.
\n
As noted in the previous release (v0.20.0), the Asmap mechanism was implemented to defend against the so-called Erebus attack, which in theory could disrupt exchanges or mining pools.
\n
Follow ForkLog’s news on Facebook!