-
Notifications
You must be signed in to change notification settings - Fork 347
Add P2PKH transparent input support to transaction::Builder #107
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
str4d
merged 10 commits into
zcash:master
from
str4d:transaction-builder-transparent-inputs
Nov 13, 2019
Merged
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
42b7f32
legacy::Script::address
str4d 70857b0
Pass Script to signature_hash by reference
str4d 3425eab
transaction::Builder::add_transparent_input()
str4d 5a177ee
Make mod serialize public
adityapk00 fab9160
transparent inputs should use serialize_der()
adityapk00 885e09a
Create OutPoint from hash and n
adityapk00 b479981
Implement clone for some structs
adityapk00 d9d50b9
Move transparent signing onto TransparentInputs
str4d 8d967c8
Move transparent input pushing onto TransparentInputs
str4d 8d6f882
Renames after moves
str4d File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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 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 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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Dependency is pinned until rust-bitcoin/rust-secp256k1#150 is resolved, because we don't want to pull
rand0.6 into our dependency tree (and we aren't using therandfeature ofsecp256k1).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have they fixed this yet? (Issue isn't closed but they seem to have merged some things.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They merged a fix, and then immediately reverted it because they had more point releases to make, and the fix for this requires a minor version bump.