Repository navigation
Migrate Bitcoin Script to Noble secp256k1 3 and hashes 2 - #18
Merged
systemslibrarian merged 3 commits intoOct 12, 2026
Merged
Conversation
Bumps [@noble/secp256k1](https://github.com/paulmillr/noble-secp256k1) from 2.3.0 to 3.2.0. - [Release notes](https://github.com/paulmillr/noble-secp256k1/releases) - [Changelog](https://github.com/paulmillr/noble-secp256k1/blob/main/CHANGELOG.md) - [Commits](paulmillr/noble-secp256k1@2.3.0...3.2.0) --- updated-dependencies: - dependency-name: "@noble/secp256k1" dependency-version: 3.2.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
deleted the
dependabot/npm_and_yarn/noble/secp256k1-3.2.0
branch
October 12, 2026 01:55
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.
Bumps @noble/secp256k1 from 2.3.0 to 3.2.0.
Release notes
Sourced from @noble/secp256k1's releases.
... (truncated)
Changelog
Sourced from @noble/secp256k1's changelog.
... (truncated)
Commits
04c95fbRelease 3.2.0.58810d5readme9a797beClarify benchmarka94be09Bump devdeps. Switch property tests to jsbte41d31bSnapshot better. Validate recovered id in verify.39146c7Add testsc431edbReduce code size: 4.76 to 4.68kbb95d37fReduce code size: 4.93 to 4.76kbab560b1Add better benchmark:sizee87558aAdd changelogMaintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for
@noble/secp256k1since your current version.You can trigger a rebase of this PR by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)Maintenance integration review: independently reviewed all six changed files and verified 133 historical evidence receipt hashes. The paired secp256k1 3.2.0/hashes 2.4.0 migration explicitly preserves Bitcoin double-SHA256 through prehash:false in all signing/verification entrypoints; native OpenSSL positive and extra-hash negative controls detect a matching sign/verify trap. All original assertions, budgets and workflow source are preserved. Exact candidate 3681683 Node24 run 38192256290 passed 49 units, 8 production smoke cases and all 43 browser cases. Historical local timing failures remain in evidence; a later original-budget 49-case local run passed. Normal integration is followed by separate main CI, Pages, artifact and actual public verification.