Skip to content
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

Parse Schnorr Pub Key & Implement TaprootSigVerifierImpl::new #267

Closed

Conversation

supreme2580
Copy link
Contributor

  • issue #
  • follows contribution guide
  • code change includes tests
  1. parse_schnorr_pub_key : uses the reference from btcd https://github.com/btcsuite/btcd/blob/master/btcec/schnorr/pubkey.go#L23
  2. TaprootSigVerifierImpl::new: uses the reference from btcd https://github.com/btcsuite/btcd/blob/24eb815168f49dea84767817717a11bd7928eb23/txscript/sigvalidate.go#L313

Copy link

vercel bot commented Oct 19, 2024

@supreme2580 is attempting to deploy a commit to the keep-starknet-strange Team on Vercel.

A member of the Team first needs to authorize it.

@Jeanmichel7
Copy link
Contributor

It would be wise to make your PR against #225

or merge the PR feat:Taproot into main before? @b-j-roberts

@supreme2580
Copy link
Contributor Author

@Jeanmichel7 do you mean I should pull from feat:Taproot into my own branch?

@Jeanmichel7
Copy link
Contributor

@Jeanmichel7 do you mean I should pull from feat:Taproot into my own branch?

No, instead, make the pull request from your branch to the feat/taproot branch, since TaprootSigVerifier already has the structures.

@supreme2580
Copy link
Contributor Author

Ohhh I see... thanks

@supreme2580 supreme2580 changed the base branch from main to feat/taproot October 22, 2024 09:23
@supreme2580 supreme2580 changed the base branch from feat/taproot to main October 22, 2024 09:29
@supreme2580 supreme2580 closed this by deleting the head repository Oct 22, 2024
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.

2 participants