IMPORTANT UPGRADE
Client 13.2.1.0 is a strongly recommended upgrade due to fixes of an edge case scenario that can cause the client to go out of sync and/or follow incorrect forks. Failure to update may increase the risk of forking from the main chain and loosing peers.
Fixes
157220e Occasionally windows clients will experience a data corruption while reading the block index from disk and shutdown. This commit allows the client to prompt for a reindex to rebuild the block index directly from disk, rather than shutting down.
48284ed In some edge cases when the client re-organizes the chain (such as a fork or orphan chain) spread fee protocol fee calculations break. Block fees are stored in a field in the block index, and when a block is disconnected it stays in the index in case it is reconsidered at a later time. When the block is disconnected the value of the bock fees field persisted. If that block was later reconsidered, the fee would increment, causing a false inflation of the calculated fees within the spread fees protocol. This commit forces the fees field to reset whenever the block is re-considered, preventing the fee incrementation.
30af9f3 At or around block 5312140 the vast majority of clients on the chain experienced a fee inflation related to bug 48284ed above. The inflated fees were recorded in the main chain, causing a small number of clients to stop syncing at this height. This commit adjusts the expected fees for this period, allowing all clients to correctly sync.
Improvements
3008c59 Only update transaction count and status for the last 2000 transactions in the transaction history page. Before this change the GUI updates the number of confirms displayed for each transaction in the list every time a new block is found on the network. This becomes a problem for wallets with large numbers of transactions as it will cause the GUI to re-draw the entire list. Benchmarking indicates that for every 16k transactions in the list the GUI will freeze for about 1 second (1000ms). In order to keep GUI paints to 200ms or less, only the latest 2000 transactions will be updated. This is a display only change, and no changes were made to the core database or internal accounting of the wallet.
81f8c34 In some cases, malformed HTTP headers in RPC responses can cause the client to crash. This only appears in windows, but this commit forces correct date formatting in all headers for all http responses.
b3c5d83 This commit updates berkeleyDB to 6.2.38 fixing a bug where some inputs tracked in the utxo set would get lost. This was an issue with BDB, not the Validity client.
8362aa2 This commit removes the forced rescan of transactions that was implemented to overcome the missing inputs issue from older BDB. Practically, it improves wallet loading times.
8b5e1c1 Cleans up code in the overview page of the GUI. Moves setting of values which only need to be set once into the constructor to prevent repeated repaints.
Housekeeping
4c985ac Periotic update of syncing checkpoints.