Protocol Notices

NavCoin is an open source protocol to which anyone can contribute. The NavCoin Core developers have enacted a policy to provide fair opportunity for any interested party to review all changes they make to the NavCoin protocol prior to public release.
View Latest Release

4.2.1 Soft Fork Now Locked In

  • Craig MacGregor
  • 28 Jun 2018

The soft forks in version 4.2.1 have now achieved lock in with an 82% approval, and will soon activate two changes to NavCoin’s consensus mechanism. All users are required to update to 4.2.1 by block 2237760 to remain connected to the network.

NavCoin 4.2.1 - 32Bit NTP Sync Hotfix

  • Craig MacGregor
  • 11 Jun 2018

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 4.2.0 NavPi Patch Notice

  • Craig MacGregor
  • 6 Jun 2018

NavCoin Core 4.2.0 was released today which includes the NTP server check to make sure every device has their system clock synced correctly when minting blocks. An unforeseen issue has been found when updating the NavPi using the updater script.

NavCoin 4.2.0

  • Craig MacGregor
  • 6 Jun 2018

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.

NavCoin Core 4.2.0 Release Candidate

  • Craig MacGregor
  • 27 May 2018

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: