-
Notifications
You must be signed in to change notification settings - Fork 71
Release 2.0.5 #59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Release 2.0.5 #59
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit is extracted from upstream PR: bitcoin/bitcoin#11367
Co-authored-by: Simon <simon@bitcartel.com>
Dependency Updates This updates: - Boost from 1.66.0 to 1.69.0 - OpenSSL From 1.1.0h to 1.1.1a - Proton from 0.17.0 to 0.26.0 - Rust from 1.28.0 to 1.32.0
Add Sapling benchmarks to benchmark runner Follow-up to #3611. Once this is merged, we can add the Sapling benchmarks to CI.
Improve some error messages when building a transaction fails Follow up from #3646
Add missing author aliases This adds some missing author aliases to release-notes.py.
Port getblockchaininfo.size_on_disk from BTC master Closes #3630.
redirect and update source docs also, update Zcash logo source. User guide related documentation in the `/doc` folder should really live in RTDs. I've left policy and process related docs as is for now. This **should not** be merged until https://gitlab.com/zcash-docs/zcash-docs/merge_requests/90 is for associated redirect links to work.
Change expiry delta for migration transactions to 450 blocks Documentation: to be done as part of the ZIP 308 update (zcash/zips#229). Test plan: manually check that migration transactions have the expected expiry height, using getrawtransaction $TXID 1. Closes #3999
Add Logging and persist async operation for Sapling migration Currently zcashd will automatically remove the last async migration operations when it reaches the height where it sends the transactions it just made. This is not in alignment with other async operations, which are not removed until a node is restarted or a user calls `z_getoperationresult`. This PR removes the calls to pop the operations so that they can be accessed and reviewed later. In this PR I also correct the operation's `amount_migrated` field to exclude the transaction fee (this field existed for debugging purposes, but should be consistent with `z_getmigrationstatus`), and have included the list of migration txids in the operation's result (this is similar to the async rpcs such as `z_sendmany`). Documentation: none needed. Test plan: * After migration transactions have been created, list the opids and call `z_getoperationresult` on them. * Check that the operations' `amount_migrated` fields exclude the fee.
Notable changes for v2.0.5-2
Release v2.0.5 2
Let's use the chainparams passed into the function rather than the static class instance.
Check timestamp is within the allowed 5 minute window to help decrease effectiveness of timewarp attacks
This commit implements some basic reorg protection by implementing a rolling 10 block checkpoint. This limits the number of blocks that a miner can mine in secret to a maximum of 10.
Use the -disablereorgprotection flag to disable reorg protection.
cryptorex
approved these changes
May 30, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This release includes the following:
Release to go live on block 364400