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

merge queue: embarking main (fa5c842) and #815 together #823

Closed
wants to merge 2 commits into from

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Dec 30, 2024

🎉 This pull request has been checked successfully and will be merged soon. 🎉

Branch main (fa5c842) and #815 are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #815.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue main for merge:

Required conditions to stay in the queue:

---
previous_failed_batches: []
pull_requests:
  - number: 815
...

0xBEEFCAF3 and others added 2 commits December 27, 2024 11:05
…e x-only pk

Per BIP-341 if there is no script paths the internal key should still be
tapTweak'd by tG where t = TaggedHash(P_x). Before this commit the
internal key and the taproot output key are the same if no script paths
are used. This is because the tweak is the 0 scalar value so Q = P + tG
= P.

It is worth noting that Bitcoin's consensus would still accept a
non-taptweak'd internal key as it verifies a signature against whatever
pk is used in the witness program. So the outputs are still spendable, however it deviates from the spec.
@mergify mergify bot closed this Dec 30, 2024
@mergify mergify bot deleted the mergify/merge-queue/1a6d9d1550 branch December 30, 2024 13:30
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.

1 participant