Skip to content

@craigmacgregor craigmacgregor released this May 3, 2019 · 98 commits to master since this release

NavCoin v4.6.0 Release Notes

Community Fund UI

<Pull Request 428>
<Commit cbffaee>

  • Added a Community Fund tab to the core wallet
  • Ability to view and filter proposals and payment request
  • Proposals and payment requests can be voted on and created
  • Removed the old Community Fund UI

Accumulation of staking rewards in different address

<Pull Request 401>
<Commit 2fb7b47>
This features introduces support for the -stakingaddress launch argument which sets a NavCoin address where the staking rewards are accumulated. It also allows you to specify mappings from one address to another, such that the first address's staking rewards will be deposited in the second address.

stakingaddress can take:

  • one argument (i.e. one NavCoin address), e.g. -stakingaddress=NxxxxMyNavCoinAddressxxxxxxxxxxxxx; or
  • a JSON argument, mapping several staking addresses to corresponding receiving addresses, e.g. -stakingaddress={"NxxxxMyStakingAddress1xxxxxxxxxxxx":"NxxxxMyReceivingAddress1xxxxxxxxxx","NxxxxMyStakingAddress2xxxxxxxxxxxx":"NxxxxMyReceivingAddress2xxxxxxxxxx","NxxxxMyStakingAddress3xxxxxxxxxxxx":"NxxxxMyReceivingAddress3xxxxxxxxxx"}. One staking address in the JSON argument can also be set to all and stakes from any staking address will be sent to the receiving address unless otherwise specified, e.g. -stakingaddress={"all":"NxxxxMyReceivingAddressALLxxxxxxxx",...}

Not compatible with cold staking.

Mnemonic seed phrase support

<Pull Request 400>
<Commit 375c657>
This PR adds a new RPC command to export the existing master private key encoded as a mnemonic:
dumpmnemonic It admits an argument specifying the language.
Support for two new wallet options (-importmnemonic and -mnemoniclanguage) have also been added to allow to create a new wallet from the specified mnemonic.

Fix wrong balance after orphan stakes

<Pull Request 438>
<Commit 4041e3e>
This PR fixes an historical issue which made the wallet show a wrong balance after orphan stakes.

Index cold staking address unspent output by spending address

<Pull Request 434>
<Commit 404d85f>

When running a node with -addressindex=1 executing the RPC command “getaddressutxos” with the spending pubkeyhash of a cold staking address will now return any utxo’s available to spend by that key including those where the pubkeyhash is the spending key of a coldstaking transaction. Previously only regular utxo’s sent directly to that pubkeyhash were returned.

Fix for Payment Request reorganizations

<Pull Request 456>
<Commit 688bf4d>

This PR prevents payment requests with invalid hashes (not set yet or out of the main chain) to count for the already requested balance of a proposal.

Other updates to the NavCoin client, docs and codebase

SHA256 Hashes

To check the validity of the hashes, visit the navcoin-sigs repository

navcoin-4.6.0-aarch64-linux-gnu.tar.gz

5837fa19f4b5784871f081d06bcef14ff67b9b0bab1037333b7c514fa0e8e652

navcoin-4.6.0-arm-linux-gnueabihf.tar.gz

0ec939fa648a08583a40972d652af3d630f198a9eb38557b94bffabe5eb5b32f

navcoin-4.6.0.tar.gz

e8c56e47e99af1d41eb05ee961258c8ca4c1822b7a5e72c7961cb32650f2c72f

navcoin-4.6.0-osx.dmg

d99e812e574142913607a20ced1a6691018c15b53629a8ca62b2a383dd94b5b0

navcoin-4.6.0-osx64.tar.gz

b6fed840638e553f342ea439d33baf78b070b0b767651c156a7743ae6aa65c7d

navcoin-4.6.0-x86_64-linux-gnu.tar.gz

a82ca18c2a3767a1f895080632e43fe65c46465eaad8354ad983d44885f210ba

navcoin-4.6.0-i686-pc-linux-gnu.tar.gz

5cbba74983c5cdc39d29f726a62b1ad8e3de1c619d5e4117a68bd96883062e1d

navcoin-4.6.0-win32-setup.exe

a83e61e7a97d2247e3258909236a95fc84451c53ff83e756223f04e18798099b*

navcoin-4.6.0-win32.zip

944f6fa5994a90b7fff90a7392d8f56c8ef5909527d12bfdeb120dc03a1eff8c

navcoin-4.6.0-win64-setup.exe

35aaa6f4ea30a525a36427cab5a517e407bcf2083d15daa45fd05712f452f55e*

navcoin-4.6.0-win64.zip

e9937c91d7383fa540d350f3008813cd2adaa1795e20f224593cbde4b555627d

*The hashes of Windows .exe builds are currently nondeterministic. The hashes shown here will match the binaries attached to this release, but if you build from source you will end up with a different checksum. Users who are concerned with the checksums of .exe builds should compile their own builds to verify this.

Assets 14
You can’t perform that action at this time.