Merged
Conversation
feat: add support to P2WPKH, P2WSH and P2TR
Flyover 2.1 -> QA-Test
Gh policy sync
chore: update actions versions
Bumps the npm_and_yarn group with 1 update: [secp256k1](https://github.com/cryptocoinjs/secp256k1-node). Updates `secp256k1` from 4.0.3 to 4.0.4 - [Release notes](https://github.com/cryptocoinjs/secp256k1-node/releases) - [Commits](cryptocoinjs/secp256k1-node@v4.0.3...v4.0.4) --- updated-dependencies: - dependency-name: secp256k1 dependency-type: indirect dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <support@github.com>
…yarn-38c118d439 chore(deps): bump secp256k1 from 4.0.3 to 4.0.4 in the npm_and_yarn group
Qa test sync
MaximStanciu8
approved these changes
Nov 4, 2024
AndresQuijano
approved these changes
Nov 13, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Merging the native segwit changes support
Why
We got security approval and QA validation over this changes so we're in conditions of merging to master. We can merge to master because this project is not deployed but published on npm