Skip to content

Conversation

@matthiasgeihs
Copy link
Contributor

@matthiasgeihs matthiasgeihs commented Dec 11, 2024

adds support for bip340 key tweaking, as required for bip341 taproot transactions.

requires:

  • publish updated client
  • deploy updated server

@matthiasgeihs matthiasgeihs force-pushed the feat/bip340-key-tweak branch 2 times, most recently from a207727 to b589d24 Compare December 12, 2024 16:23
@matthiasgeihs matthiasgeihs marked this pull request as ready for review December 16, 2024 11:15
@matthiasgeihs matthiasgeihs force-pushed the feat/bip340-key-tweak branch 2 times, most recently from b97f09f to ef224dd Compare December 16, 2024 11:56
- quick fix session time test
- quick fix sync error
- quick fix loginWithSFA return type
Copy link
Member

@himanshuchawla009 himanshuchawla009 left a comment

Choose a reason for hiding this comment

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

lgtm

} else if (this._sigType === "ed25519" || this._sigType === "bip340") {
return this.sign_frost(data, hashed);
if (opts?.hashed) {
throw CoreKitError.default(`hashed data not supported for bip340`);
Copy link
Member

Choose a reason for hiding this comment

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

i think at this point we should streamline this hashed parameter, having it supported for one sig type and not for others increases integration and doc effort. Either we should drop the support of it completely or should make it consistent.

Happy to create a diff issue for that.

@himanshuchawla009 himanshuchawla009 merged commit b885897 into v4 Dec 17, 2024
1 check passed
@himanshuchawla009 himanshuchawla009 deleted the feat/bip340-key-tweak branch December 17, 2024 04:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants