NavCoin v4.7.1 Release Notes

Fix CFund DB read after nullified entry

This patch fixes a bug where a cfund database entry that was previously deleted is still persisting, preventing future writes of the entry. This can happen in a scenario where a proposal is included in a block which is invalidated (because of a reorganization) which is then included in a new block as part of the new longest chain.

This fix is the main purpose of the 4.7.1 patch release, while preparing this bugfix there were several other PR’s merged which are also included in this release.

Merged PRs

Pull Request 509 Commit 40eac7ab Updated some NULL -> nullptr
Pull Request 525 Commit 8ed8cf87 Replaced all BOOST_FOREACH calls with new for() syntax (c++11)
Pull Request 527 Commit b2921285 Updated the custom ‘change’ address to be a persistent setting #527
Pull Request 546 Commit e1870814 Added new -allindex option
Pull Request 554 Commit 82523147 Replaced Q_FOREACH with for() from c++11 standard
Pull Request 560 Commit 762c3ffd Set pindexDelete to nullptr on intialize
Pull Request 561 Commit 130ddf4a Fixed some gitignore permissions and added new file to main gitignore
Pull Request 566 Commit 6de5f909 Updated includes syntax based on discussion on #503
Pull Request 578 Commit c464383b Sort available coins for staking by coin age descending
Pull Request 587 Commit ff6f543e Add support for raw script addresses
Pull Request 603 Commit f755e298 Updated depends to use winssl for windows and darwinssl for osx
Pull Request 605 Commit 5e0af830 Staking reward setup GUI
Pull Request 611 Commit 30401b32 Fixed error.log loading in Debug Window (Windows)
Pull Request 612 Commit d5cfa467 Fix random RPC tests failing
Pull Request 614 Commit 80323b33 Patch for staking redirect gui
Pull Request 615 Commit 9e84d40a Bump version number

For additional information about new features, check https://navcoin.org/en/notices/