Bump @noble/secp256k1 from 3.0.0 to 3.1.0 in /frontend

[dependabot]

Bumps @noble/secp256k1 from 3.0.0 to 3.1.0.

Commits

• f61f685 Release 3.1.0.
• 30841b9 Minor fixes
• 943f916 Implement changes as per Mar 2026 audit.
• f982d7d Bump typescript to 6.0.2
• 4639c0f Fix tests
• 7c74a5a Add docs everywhere. Upgrade to ts 6.0-rc, jsbt 0.5. Add pkg.json scripts.
• 18cf7c0 Merge pull request #141 from Zosoled/bugfix/p-documentation
• 0f3c1e9 Fix P documentation in .ts
• 3e1e0ce Merge pull request #140 from Zosoled/bugfix/p-documentation
• f7cb2dc Fix P documentation
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​noble/secp256k1 since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

Provenance Attestation Check Failed

This pull request has been automatically closed because the following dependencies do not have provenance attestation:

Failed: @noble/secp256k1

What is provenance attestation?

Provenance attestation cryptographically proves that a package was built from a specific source repository using a specific build process. This helps protect against supply chain attacks by verifying the link between published packages and their source code.

What to do

• Check if a newer version of the dependency publishes provenance
• Contact the package maintainer to request npm provenance support
• If this dependency is trusted and an exception is warranted, a maintainer can reopen this PR and add the provenance-exception label

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.