Reddcoin (RDD) Core Wallet – v3.10.2 – DoS Mitigation and Peer Management Update
Reddcoin Core v3.10.2 is now in general release and available from:
This is an IMPORTANT new minor version release, bringing the ability to manage, ban or disconnect down-level peers making excessive network requests or otherwise misbehaving due to PoSV v2 soft-fork. Includes bug fixes and security refinements.
Due to important peer management components and tools being needed to adjust Reddcoin’s network performance to address remaining down-level pre-PoSV v2 wallets, we have adjusted our dev inclusion schedule to enable this release of v3.10.2.
While this release does not include live “headers-first” technology, still under final testing, it DOES includes important enhancements to the wallet’s behavior with regard to older peers causing a virtual DoS (“Denial Of Service”) effect.
The code implemented in this release will help with this condition by both temporarily banning misbehaving nodes, and adding manual tools to the wallet interface peer list to act directly. No global blacklists, whitelists, or other restrictive technology have been applied, allowing such clients the ability to upgrade and rejoin the Reddcoin consensus and PoSV v2 once issue of block version is addressed.
Please report bugs using the issue tracker at github:
How to Upgrade
While the upgrade process normally does not touch the “wallet.dat” file, it is good practice to make a backup of your wallet file prior to any upgrade or downgrade operations. A simple backup can be performed using the File -> Backup… option to export a copy of the wallet file to a safe location.
If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), then run the installer (on Windows) or just copy over /Applications/Reddcoin-Qt (on Mac) or reddcoind/reddcoin-qt (on Linux).
If you want to be able to downgrade smoothly, make a backup of your entire data directory. Without this your node will need start syncing (or importing from bootstrap.dat) anew afterwards. It is possible that the data from a completely synchronised 3.10 node may be usable in older versions as-is, but this is not supported and may break as soon as the older version attempts to reindex.
This does not affect wallet forward or backward compatibility.
3.10.2 Change log
4db53d7– Jonas Schnelli, 2015-06-19 : fix missing lock in CNode::ClearBanned()
1d0dd29– Jonas Schnelli, 2015-06-12 : setban: add RPCErrorCode
f9cc1c9– Jonas Schnelli, 2015-06-12 : fix CSubNet comparison operator
2074e33– John Nash, 2020-07-30 : allow absolute bantime
0a6433a– Jonas Schnelli, 2015-06-12 : rename json field “bannedtill” to “banned_until”
886bded– Jonas Schnelli, 2015-05-25 : [RPC] extend setban to allow subnets
302b06f– Jonas Schnelli, 2015-05-19 : [net] remove unused return type bool from CNode::Ban()
345d46a– Jonas Schnelli, 2015-05-19 : [QA] add setban/listbanned/clearbanned tests
67cae75– Jonas Schnelli, 2015-05-19 : [RPC] add setban/listbanned/clearbanned RPC commands
2ab1e23– Jonas Schnelli, 2015-05-19 : [net] extend core functionallity for ban/unban/listban
fb2765e– Alex van der Peet, 2015-06-11 : New RPC command disconnectnode
4c41d2f– Philip Kaufmann, 2015-06-01 : [Qt] disconnect peers from peers tab via context menu
33d8302– John Nash, 2020-07-11 : update staking icon status when wallet (un)lock is toggled
c8e31ef– John Nash, 2020-07-07 : Select a specific commit to use for gitian-builder