Skip to content
This repository was archived by the owner on Jan 25, 2024. It is now read-only.

Zcash: add setConsensusBranchId() to TansactionBuilder#90

Merged
matthewzipkin-bitgo merged 5 commits intoBG-22830-update-zec-heartwoodfrom
BG-24753-ZEC-consensus-branch-id-rebase-1.7.1
Oct 26, 2020
Merged

Zcash: add setConsensusBranchId() to TansactionBuilder#90
matthewzipkin-bitgo merged 5 commits intoBG-22830-update-zec-heartwoodfrom
BG-24753-ZEC-consensus-branch-id-rebase-1.7.1

Conversation

@matthewzipkin-bitgo
Copy link

@matthewzipkin-bitgo matthewzipkin-bitgo commented Oct 16, 2020

#89 but rebased on v1.7.1

TICKET BG-24753

@matthewzipkin-bitgo matthewzipkin-bitgo changed the base branch from v1.7.1 to BG-22830-update-zec-heartwood October 16, 2020 16:57
@matthewzipkin-bitgo matthewzipkin-bitgo changed the title Bg 24753 zec consensus branch id rebase 1.7.1 Zcash: add setConsensusBranchId() to TansactionBuilder Oct 16, 2020
Also including README in test directory to explain how to generate test vectors for the NEXT upgrade TICKET BG-24753
@matthewzipkin-bitgo matthewzipkin-bitgo force-pushed the BG-24753-ZEC-consensus-branch-id-rebase-1.7.1 branch from cd7d578 to 6e7ba05 Compare October 16, 2020 17:02
Copy link
Contributor

@argjv argjv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Update package.json version and LGTM

@matthewzipkin-bitgo
Copy link
Author

matthewzipkin-bitgo commented Oct 20, 2020

Ok thanks - still making sure it runs correctly as a dep to wallet-platform. Once I'm confident it works I'll come back and merge. Also should we call this version 1.7.2? My concern is if its required using ^ then some package that isn't ready (doesn't have consensus ID set) will pull it down anyway -- but we already have a 1.8.x and 1.9.x I think. So...?

Copy link
Contributor

@OttoAllmendinger OttoAllmendinger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so this only affects how we are building new zcash txs, not how existing ones are parsed?

@@ -0,0 +1,126 @@
# Generate test vectors for new ZCash testnet consensus branch IDs
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

awesome!

long-term we should have a script for this, but we can tackle that when we overhaul this lib

@OttoAllmendinger
Copy link
Contributor

the fact that this changes the default way zcash transactions are built actually suggests we bump the minor version

Alternatively we could instead release a version of this lib that supports the new consensusBranchId in a convenient way without defaulting to it. That way we can decide at the callsite somehow.

Copy link
Contributor

@OttoAllmendinger OttoAllmendinger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually I realized that this is for an old version. New development should happen on the master branch.

@argjv
Copy link
Contributor

argjv commented Oct 26, 2020

We are releasing 1.7.2 because the latest version in master breaks platform and other places. Fixing utxo-lib is not in the roadmap.

@matthewzipkin-bitgo matthewzipkin-bitgo merged commit 6e64d47 into BG-22830-update-zec-heartwood Oct 26, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

3 participants