New wallet version 2.0.5.7
Release URL:
https://github.com/DMDcoin/Diamond/releases/tag/diamond2057This wallet is not mandatory. However, due to new functionality and improved CPU usage it is highly recommended especially for loaded nodes, such as those that mine/mint, pools and exchanges. It should also improve performance for everyone.
Binaries for Windows and OS X (tonight) are provided. Just replace your own binary. If you build form source, stop old binary, start new binary. No other update action is required.
Changelog:
Optimizations to call hash calculation functions less.
Small optimization to Groestl hash routine.
Ban nodes that are disconnected due to old version/protocol.
Implement -zapwallettxes, borrowed/adapted Bitcoin code.
Implement ACL for connected nodes.
Fix bugs in seed node processing.
Add and activate seed nodes to facilitate bootstrap without config file.
Turn IRC off by default. (IRC may be removed in future)
Increase maximum number of outgoing connections to 16
Limit output to log file if debug is disabled.
Update wallet version to 2.0.5.7
Of special interest is -zapwallettxes. This command switch (or config file option) will wipe out any existing transactions in the wallet, then initiate rescan of the block chain (slow!) to find out the valid transactions for your coins. If used as -zapwallettxes=1 it would also preserve transaction comments etc. If used as -zapwallettxes=2 it will do a clean rebuild of the transactions without those details. If you put it in the config file, make sure you remove it after first use, as it will do the same (slow!) thing every time you start your wallet.
If you run a busy wallet, that sends a lot of (not PoS) transactions you might want to run this periodically to make sure your wallet transaction acconting is in sync with the block chain.
The new wallet is able to start without any config file. It would then use the seed nodes to find out about other nodes and connect to them as well. This lets us get rid of IRC in some o the next updates.
The new wallet code also makes certain optimisations to reduce the number of hash function calls for each block. More optimisations are planned in this area to improve CPU usage further. It also reduces the amount of log file output, if debug is disabled to reduce storage I/O load.