zcash

UPDATE: We are aware of an issue that causes nodes running v1.0.10 to be unable to connect to other nodes, and vice versa. Users are advised to upgrade to v1.0.10-1, which fixes the issue.

This release includes privacy and performance improvements, as well as bug fixes.

Summary of the changes included in this release:

1. We improved the privacy of transactions created by our wallet that pay from shielded addresses to transparent addresses. The new version conceals more information about shielded note values in chained JoinSplit transactions. (#2440)
2. We improved reindexing and block download performance by switching to libsecp256k1 for transparent signature validation. (#2335, stats)
3. We added a config parameter to reject transactions from the mempool by number of transparent inputs. This is a short-term workaround to handle periods of high network load, and will be replaced in the future by a more comprehensive mechanism. (#2342)
4. We merged several build system portability fixes. (#2412, #2420, #2436)

For a more complete list of changes, see our 1.0.10 milestone.

This release fixes a security vulnerability detected in versions starting with 1.0.4 up to and including 1.0.8. More information on this vulnerability and risks to users are detailed in the related security announcement.

Summary of the changes in this release:

1. Fix a Denial of Service vulnerability that could cause nodes receiving a specially crafted transaction into their mempool to crash.
2. Simplify the calculation of priority for shielded transactions.

This release is our first with the auto-deprecation feature described in our Release Cycles and Lifetimes post. It also introduces opt-in support for the AMQP protocol.

Summary of the changes in this release:

1. Implemented automatic deprecation shutdown. (#2297)
2. Added opt-in AMQP support. (#2189, #2362, #2280)
3. Performance benchmarking and testing improvements: fix hang in benchmarking CI automation, add connectblockslow benchmark, re-enabled miner tests, improved error reporting in rpc-tests framework, changed default regtest port. (#2397, #2372, #2389, #2376, #2265, #2270)
4. Automated the release process, added build diagnostics for better user support, and fixed versioning problems in debian packaging and manpages. (#2393, #2369, #2281)
5. Added test for pairing bug when G1 is infinity. (#2399)
6. Documentation: Clarify release policy, added wallet backup instructions, and fixed some incorrect references to "bitcoin". (#2401, #2340, #2364, #2338)
7. Added alert sources for 2017-04-13 security incident. (#2293)

For a more complete list of changes, see our 1.0.9 milestone.

This release focuses on backporting features from upstream Bitcoin and usability improvements to the RPC interface. For more information please visit: https://z.cash/blog/new-release-1-0-8.html

This release fixes several documentation issues with the 1.0.7 release.

Upcoming Testnet Upgrade

The Zcash testnet will soon be upgraded in order to resolve an issue with the Testnet Founders Reward addresses. This will not affect the main Zcash network. Testnet users must upgrade to at least version 1.0.7 by block 53127, as that is when the testnet network changes will take place. Users who do not upgrade may be left on their own chain, contributing to a chain fork.

This release focuses on updating Zcash to be compatible with upstream changes, fixing bugs, and adding alerts, tests, and checkpoints.

Upcoming Testnet Upgrade

The Zcash testnet will soon be upgraded in order to resolve an issue with the Testnet Founders Reward addresses. This will not affect the main Zcash network. Testnet users must upgrade to at least version 1.0.7 by block 53127, as that is when the testnet network changes will take place. Users who do not upgrade may be left on their own chain, contributing to a chain fork.

Summary of the changes in this release:

1. Pull in upstream changes related to testing, the RPC interface, as well as others. (#2099, #2100, #2101)
2. Keep a record of alerts sent to mainnet. (#2093)
3. Pause mining during joinsplit creation. (#1932)
4. Fix bug in testnet and update Founder’s Reward addresses. (#2114)
5. Large shielded transactions using the default fee are no longer treated as "free" transactions. (#2141)
6. Improve auto-generated manpages. (#2124)
7. Add checkpoint on testnet and mainnet. (#2128, #2126)

For a more complete list of changes, see our 1.0.7 milestone.

This release focuses on improving functionality and usability of low-level interfaces used by external software interfacing with Zcash, and on bolstering several security components.

Summary of the changes in this release:

1. Users can now mine to a single address by using new zcashd options -mineraddress and -minetolocalwallet (#1965, #2081)
2. Updated RPC calls getrawtransaction and decoderawtransaction to display all fields of a JoinSplit. Now includes the zk-proof, ephemeral key, random seed and encrypted ciphertexts (#2054)
3. Updated logging in RPC call z_sendmany for the debug categories zrpc and zrpcunsafe (#2058)
4. Fixed a bug which prevented passing a fee parameter of zero to RPC call z_sendmany (#2068)
5. Added build option --disable-mining to zcutil/build.sh to allow removal of mining code when compiling (#1836)
6. ZeroMQ notification support has been backported (#2050)
7. Upgraded OpenSSL to 1.1.0d (#2051). We now also use libsodium’s CSPRNG instead of OpenSSL’s (#1706)
8. Backported and updated UniValue library to replace usage of JSON Spirit library (#1990, #2082)
9. Removed unnecessary exceptions from libsnark (#2080)
10. Added zcashd option flag -experimentalfeatures (#2056), fixed a bug in a test (#2078) and updated documentation (#2069, #2077)

For a more complete list of changes, see our 1.0.6 milestone.

This release includes a variety of bugfixes and usability improvements.

Summary of the changes in this release:

1. The chain is now fully rescanned when keys are imported that are older than the wallet. (#1978)
2. The number of commitments in the note commitment tree is now displayed by getblockchaininfo. (#1946)
3. zcash.conf now must exist in order to start zcashd. (#2013)
4. Fixed a bug where z_sendmany logged incorrect txid fragments when sending from transparent addresses. (#1980)
5. We integrated upstream's cookie-based RPC authentication. (#1999)
6. We added a restriction to wallet export paths to protect user security. (#2006)
7. z_getoperationstatus is now sorted chronologically. (#2015)
8. Messages containing newlines are now rendered properly by the metrics UI. (#1972)
9. We added more tools for benchmarking JoinSplit creation. (#1953)
10. We now show serialized transaction size in listtransactions, more operation details in z_getoperationstatus, and the age of the note being spent in z_sendmany logging. (#2001, #1976, #1977)
11. We now instruct users to run fetch-params if the parameters could not be found locally. (#1979)
12. We handle exceptions better in some situations for more user-friendly error messages. (#1976)

For a more complete list of changes, see our 1.0.5 milestone.

This release fixes several bugs, improves performance, and adjusts mining policies. With this release, private payments will get relayed and mined faster.

Summary of the changes in this release:

1. We fixed a cache invalidation bug that caused some orphaned blocks to trigger node crashes. (#1928)
2. We fixed a race condition that inhibited creation of multi-JoinSplit transactions. (#1911)
3. We adjusted mining policies to encourage inclusion of transactions containing JoinSplits. (#1895, #1902)
4. We improved rescan and reindex performance. (#1892, #1904)
5. We improved zk-SNARK verification performance by 7%. (#1919, stats)
6. We added additional well-formedness checks for JoinSplit proofs. (#1938)
7. We added a fee parameter to z_sendmany. (#1907)
8. We added a getlocalsolps RPC method for obtaining the mining rate without the metrics screen. (#1642)
9. The Bash completion files were updated to work with zcashd. (#1909)
10. The build scripts were extended to make porting Zcash to other platforms easier. (#1905)
11. A checkpoint was added at block height 15,000. (#1865)

For a more complete list of changes, see our 1.0.4 milestone.

This release fixes several crashes and security bugs, improves performance, and adjusts relay policies.

We strongly recommend users and miners update to this version, as it fixes a cache invalidation bug that could be used by an attacker to disrupt the network. (See #1874.)

Other changes in this release include:

1. We fixed a bug that caused the wallet to crash during startup in some situations, such as when the wallet is not synchronized properly with the blockchain. (#1858)
2. We re-enabled note randomization that was temporarily disabled in 1.0.2. (#1814)
3. We adjusted fee policies to reflect changes made in Bitcoin Core and encourage relaying of transactions containing JoinSplits. (#1855)
4. We improved diagnostics and strengthened testing for the merkle tree's interaction with the constraint system. (#1797)
5. We disabled RPC keepalive features temporarily to avoid deadlocks. (#1847)
6. We adjusted our use of the libsnark verification API to improve zk-SNARK verification performance by 10%. (#1760, stats)
7. We changed the error message format for z_sendmany so that amounts are displayed in units of ZEC. (#1838)

For a more complete list of changes, see our 1.0.3 milestone.

This release fixes a bug that prevented creating transactions to multiple shielded recipient addresses. This is an implementation bug in the zcashd wallet which does not impact the consensus protocol.

The list of changes included in this release:

1. We fixed a bug to ensure that JoinSplit transactions to multiple z-addresses will succeed. (#1790)
2. We changed z_sendmany to check if the size of a transaction for a given number of outputs will be valid. (#1808)
3. We fixed a bug that could crash the miner when it was interrupted. (#1778)
4. Community contributors helped improve our documentation. (#1765, #1763)

For a more complete list of changes, see our 1.0.2 milestone.

This release fixes a few bugs and improves diagnostics:

1. Fixed a bug where transactions that contain shielded payments were not being mined in some circumstances. (#1718)
2. Invalid arguments passed when building JoinSplits now produce more descriptive errors. (#1752)
3. Added new RPC call, z_validateaddress (#1748)
4. The friendly metrics screen has improved accuracy and additional information. (#1735)
5. A consensus rule improperly applied to the genesis block was adjusted. (#1754)
6. fetch-params.sh has been improved and is included in the gitian build. (#1758, #1759)
7. A checkpoint was added for block 2500. (#1750)

For a more complete list of changes, see our 1.0.1 milestone.