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.
Purple Zebra is the culmination of the last few months of work on NavCoin Core and includes 40 closed pull requests, many new features and important security updates & stability fixes. Due to the security patches, upgrading to Purple Zebra should be considered mandatory and performed as soon as possible, especially if you are staking.
NavCoin Core 4.5.0 has been released today which marks the last significant update to NavCoin Core of 2018. This release includes two important consensus soft forks which will bring greater security to the network and to individuals funds; Cold Staking and Static Rewards.
The issue preventing NavPi users from successfully upgrading to 4.2.0 has now been patched with version 4.2.1. If you are using the NavPi and want to support the community fund accumulation soft fork make sure you update now and resume staking with the new version.
NavCoin Core 4.2.0 is now available for download. This update includes two important soft forks. One kick starts the accumulation of the community fund while the other adds NTP server syncing to ensure all blocks are submitted with the correct timestamp. Please make sure you update your wallet if you want to see these soft forks enabled.
The NavCoin Core developers have enacted a policy to create a release candidate and publicly notify all interested parties of any important updates prior to merging the changes into the master branch. This release schedule will be formalised into a process document to be published on the NavCoin.org website in the near future as reference. There are two reasons for this update: