chore(vendor): update secp256k1-zkp to v0.7.1
What the developer wrote
Authored by M1nd3r
chore(vendor): update secp256k1-zkp to v0.7.1
- Updated from v0.7.0.
- Pinned to release/commit: https://github.com/bitcoin-core/secp256k1/releases/tag/v0.7.1
- Changelog: https://github.com/bitcoin-core/secp256k1/blob/master/CHANGELOG.md#071---2026-01-26
- Changes: https://github.com/bitcoin-core/secp256k1/compare/v0.7.0...v0.7.1
What changed, and why it matters
This commit only updates a bundled cryptographic library (secp256k1-zkp) from version 0.7.0 to 0.7.1. The actual code change is a one-line update to the submodule pointer. The commit message does not describe any security fix, and no security-relevant details are visible in the diff itself.
Review the upstream secp256k1 v0.7.1 changelog and compare commits to determine whether this release contains any security fixes relevant to Trezor's usage. Without that external review, this commit should be treated as a routine dependency bump.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff is a single submodule pointer change in vendor/secp256k1-zkp from commit a660a4976efe880bae7982ee410b9e0dc59ac983 to 1a53f4961f337b4d166c25fce72ef0dc88806618. The commit message frames this as a routine vendor update and references upstream release notes, but those notes are not included in the provided materials. No vulnerability, bug class, or attack surface can be identified from the commit alone.
Changed components
vendor/secp256k1-zkp submoduleInspect captured patch +1 / −1
### vendor/secp256k1-zkp
@@ -1 +1 @@
-Subproject commit a660a4976efe880bae7982ee410b9e0dc59ac983
+Subproject commit 1a53f4961f337b4d166c25fce72ef0dc88806618Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.