Skip to content

Releases: ZcashFoundation/zecwallet

Zecwallet Fullnode v1.4.3: Update zcashd

01 Mar 19:35
Compare
Choose a tag to compare

This version updates the embedded zcashd to v4.3.0, which features syncing improvements.

Zecwallet Fullnode v1.4.2: Fix some sync issues

17 Feb 17:51
Compare
Choose a tag to compare

This version of Zecwallet Lite upgrades the embedded zcashd with a fix for some syncing issues. It also bumps the version number scheme to be consistent with the Lite wallet.

Zecwallet Fullnode v0.9.24: Zcashd v4.2.0

02 Jan 06:22
Compare
Choose a tag to compare

This version updates the embedded zcashd to v4.2.0

Zecwallet Fullnode v0.9.23: Win7 fix

01 Dec 21:07
Compare
Choose a tag to compare

This version of Zecwallet fullnode fixes an issue where Win 7 users weren't able to launch the embedded zcashd.

Zecwallet Fullnode v0.9.22: Bugfix

22 Nov 05:31
Compare
Choose a tag to compare

This release of Zecwallet Fullnode fixes an issue where sending the "max" amount was calculating the default fee incorrectly.

Zecwallet Fullnode v0.9.21: Update embedded zcashd to v4.1.1

18 Nov 21:46
Compare
Choose a tag to compare

Zecwallet Fullnode v0.9.20: Reduce default Fees

04 Nov 17:44
Compare
Choose a tag to compare

This release of Zecwallet Full node incorporates ZIP-313, which reduces the default Zcash transaction fee to 0.00001 ZEC. The default fee change will active around 4 weeks after the canopy upgrade (Block 1_080_000)

Also includes some minor bug fixes.

Zecwallet Fullnode v0.9.19: zcash URI support (ZIP-321)

19 Oct 18:45
Compare
Choose a tag to compare

This release of Zecwallet Fullnode now has full URI support for Zecwallet, based on the ZIP-321 standard

Zecwallet Fullnode: Canopy support

10 Sep 19:49
Compare
Choose a tag to compare

This version of Zecwallet Fullnode upgrades the embedded zcashd to v4.0.0, which supports the Capony zcash upgrade, with an activation height of 1046400.

Zecwallet v0.9.17: Fix CSV exports

30 Aug 04:21
Compare
Choose a tag to compare

This version fixes an issue with exporting CSV files of transactions, where a memo might have been interpreted as a formula, causing unexpected behaviour.

Thanks to @s-rah for reporting this issue.