v2 handshake failure falls back to v1, this downgrade design is a bit problematic. Using Tor for exit or simply disabling -privatebroadcast is more stable, hurry up with 31.1.

View Original
WuSaidBlockchainW
Bitcoin Core 31.0 - privatebroadcast feature has a privacy vulnerability
Bitcoin Core 31.0's -privatebroadcast has a privacy vulnerability: when IPv4/IPv6 node handshake fails with BIP324 v2 enabled, it falls back to v1 direct connection, exposing the transaction originator's IP without Tor. Affected are nodes that enable -privatebroadcast and broadcast via sendrawtransaction, as well as nodes capable of outbound IPv4/IPv6 connections; wallet RPC, onion, and I2P are unaffected. The fix will be released with 31.1; it is recommended to disable -privatebroadcast, disable v2, or route outbound traffic through Tor before upgrading.
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
  • Reward
  • Comment
  • Repost
  • Share
Comment
Add a comment
Add a comment
No comments
  • Pinned