Be notified of new releases
Create your free GitHub account today to subscribe to this repository for new releases and build software alongside 28 million developers.Sign up
- navcoin-4.1.0-aarch64-linux-gnu.tar.gz 4.96 MB
- navcoin-4.1.0-arm-linux-gnueabihf.tar.gz 4.63 MB
- navcoin-4.1.0-i686-pc-linux-gnu.tar.gz 20.3 MB
- navcoin-4.1.0-osx.dmg 14.2 MB
- navcoin-4.1.0-osx64.tar.gz 16.6 MB
- navcoin-4.1.0-win32-setup.exe 14.9 MB
- navcoin-4.1.0-win32.zip 20.5 MB
- navcoin-4.1.0-win64-setup.exe 15.4 MB
- navcoin-4.1.0-win64.zip 21.5 MB
- navcoin-4.1.0-x86_64-linux-gnu.tar.gz 19.8 MB
- navcoin-4.1.0.tar.gz 6.4 MB
- Source code (zip)
- Source code (tar.gz)
Community Fund Enabled on the Testnet
The community fund which we are voting to implement has been implemented to the NavCoin testnet for everyone to try. The testnet stake rewards are reduced to 4% and there is 0.25 NAV per block generated by the staker and sent to the Community Fund Smart Contract.
You can help us to test the proposal, voting and redemption smart contract features we have proposed to implement on the mainnet. We have created a new genesis block for the testnet, so if you’ve been using it previously, please re-sync once you’ve downloaded the 4.1.0 wallet.
New Majority Version Alert
We have added a feature which allows the wallet to track the version number of the other wallets on the network. If your wallet detects a majority of wallets to be on a greater version number than its own version number, it will alert you that a new update is available.
Aside from the early access features, the main priority for this release is to secure the network. Bittrex alerted us to some reported instability of the blockchain they were seeing and after some thorough investigation and we were able to find the cause and we have included a preventative security patch in this latest version of the wallet.
The main changes have been to make improvements to the script check methods and we have also added the nTime & strDzeel parameters to the signature hash. This security patch will prevent the recently seen network instabilities moving forward and resolve the issues Bittrex have reported. It will also make these changes compatible with NavPay which we are still on schedule to release later this month.
Making these security improvements to the script check is a change to the consensus mechanism and requires a majority consensus to be accepted on the network. We have decided the best course of action is to implement the security patch as a mandatory hard fork instead of waiting for a majority consensus to be organically achieved.
The network will reject blocks and transactions from versions older than 4.1.0 from 11 December 2017 @ 11:00am GMT.
The network will take some time to stabilize after the fork occurs, so we suggest not sending any NAV for up to 48 hours after the hard fork time. We will post a message to the community once we see the network is stable and we are starting to bring the exchanges back online for deposits and withdrawals.
To help stabilize the network, please update to the new client before the fork time and stake your coins to mint blocks.
To have a smooth transition to the new version, please download 4.1.0 and install it before the hard fork time is reached. If you're using the GUI you will be prompted to allow the wallet to rebuild the database. If you've running the daemon, you will need to run it with the -reindex flag before you will be able to use the new daemon.
If you're using the NavPi there are some extra steps to get up and running with the new version.
From the control panel page, click the
update button and update the UI from GitHub.
Run the updater script located at
/home/stakebox/UI/libs/updater.sh or wait for the autoupdater to run if you are on version 1.0.3 or later.
When you see the notice on the homepage of your NavPi stating that a new update has been installed, click the button to reboot the device.
When your device has rebooted, go back to the control page and click the
Reindex button and reindex the blockchain.
Note that in some instances, it will be unable to reindex the blockchain and the wallet will unfortunately be required to resync the blockchain which can take some time.
If you need to resync the blockchain, you can find a bootstrap to speed the process up here:
Full list of updates
- New genesis block for the testnet.
- Community fund enabled on the testnet.
- New block version structure. Rejects blocks with wrong version.
- Blocks will still signal version bits even after activation.
- Nodes with obsolete protocol versions get their messages rejected instead of being banned.
- Improvements in the Script check methods.
- Reason for messages being rejected are now registered in the log file.
- Signature Hash now includes nTime and strDZeel.
- Wallet is able to track other wallet’s versions and displays a warning when a majority has updated to a new version.
- New format of stake voting. Votings can be dynamically be pushed into the network. New RPC method ‘stakervote’.
- Adds ‘donatefund’ RPC method to donate to the community fund.
- Moved many consensus related parameters to chainparams.cpp
- Fixes a bug where a transaction could have a timestamp earlier than the outputs it spent.
- Fixes a bug where the staker thread could be interrupted.
- Fixes a bug which prevents node to start syncing at boot under some circumstances.