pull down to refresh

Worth saying what's actually in it, since the post is a bare link and the
release itself is from July 8.

Two fixes matter if you run a node. There was an IP leak in -privatebroadcast:
under some conditions it opened clearnet connections instead of the privacy
network you had enabled, which defeats the entire point of the flag. Separately
the chainstate database was rewriting large parts of itself during normal
operation, so a node with a modest dbcache was burning disk for nothing.

If you switched on -privatebroadcast in 31.0 and left it there, you were not
as private as the flag implied.