-
Notifications
You must be signed in to change notification settings - Fork 20.3k
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
chore: use decred secp256k1 directly #30595
Conversation
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.
LGTM, we are already indirectly depending on dcrec/secp256k1/v4 v.4.0.1 (thats why the go.sum didn't change) and getting rid of the intermediary dependency is good, esp of one that we had issues with in the past wrt. their backwards comp
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.
Can confirm that all replaces are only aliasings.
Use `github.com/decred/dcrd/dcrec/secp256k1/v4` directly rather than `github.com/btcsuite/btcd/btcec/v2` which is just a wrapper around the underlying decred library. Inspired by cosmos/cosmos-sdk#15018 `github.com/btcsuite/btcd/btcec/v2` has a very annoying breaking change when upgrading from `v2.3.3` to `v2.3.4`. The easiest way to workaround this is to just remove the wrapper. Would be very nice if you could backport this to the release branches. References: - btcsuite/btcd#2221 - cometbft/cometbft#4294 - cometbft/cometbft#3728 - zeta-chain/node#2934
Use `github.com/decred/dcrd/dcrec/secp256k1/v4` directly rather than `github.com/btcsuite/btcd/btcec/v2` which is just a wrapper around the underlying decred library. Inspired by cosmos/cosmos-sdk#15018 `github.com/btcsuite/btcd/btcec/v2` has a very annoying breaking change when upgrading from `v2.3.3` to `v2.3.4`. The easiest way to workaround this is to just remove the wrapper. Would be very nice if you could backport this to the release branches. References: - btcsuite/btcd#2221 - cometbft/cometbft#4294 - cometbft/cometbft#3728 - zeta-chain/node#2934
Use
github.com/decred/dcrd/dcrec/secp256k1/v4
directly rather thangh.neting.cc/btcsuite/btcd/btcec/v2
which is just a wrapper around the underlying decred library. Inspired by cosmos/cosmos-sdk#15018gh.neting.cc/btcsuite/btcd/btcec/v2
has a very annoying breaking change when upgrading fromv2.3.3
tov2.3.4
. The easiest way to workaround this is to just remove the wrapper.Would be very nice if you could backport this to the release branches.
References:
btcec/v2
to v2.3.4 cometbft/cometbft#3728