What the developer wrote
Authored by Salvatore Ingala
Prepare changelog for release 2.5.0
What changed, and why it matters
This commit only updates the project's changelog file to prepare for release 2.5.0. It renames an upcoming version placeholder, reorganizes release notes, and adds descriptions of user-facing changes. No source code, build scripts, or security-sensitive files were modified.
No security action required for this documentation-only commit. Review the actual code changes referenced in the changelog separately if assessing the security of release 2.5.0.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff is limited to CHANGELOG.md. It removes the ‘## [2.X.X] - XX-XX-2026’ placeholder section and inserts ‘## [2.5.0] - 24-07-2026’ with reordered and expanded release notes. The ‘Enable stack protector’ item is moved from an ‘Added’ section into ‘Changed’ and reworded as ‘Enabled stack protector.’ Descriptions of signing-display improvements, non-standard sighash settings, and BIP-87 xpub export are added. No functional code changes are present.
Changed components
CHANGELOG.mdInspect captured patch +5 / −5
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 8f84e9c..0aca666 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -7,16 +7,16 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
Dates are in `dd-mm-yyyy` format.
-## [2.X.X] - XX-XX-2026
-
-### Added
-
-- Enable stack protector
+## [2.5.0] - 24-07-2026
### Changed
- Improved the registration UX for multisig and many taproot miniscript wallet policies by showing the *clear-text, human-readable* meaning of the policy. For simple multisig policies, the clear-text description replaces the descriptor template. For a large class of supported taproot miniscript policies, it is shown *in addition to*, and *before*, the raw descriptor template. This lets the user understand the policy while still being able to compare the template against their backup.
+- Signing transactions using non-standard sighash flags now requires enabling the corresponding persistent application setting.
+- Improved the signing display for transactions using non-default sighash flags: the effective signing rule is shown, and the trusted screen now only presents amounts that the signatures actually commit to, falling back to the net amount spent/received (or a warning when nothing can be shown reliably) instead of a potentially misleading breakdown.
+- Improved the signing display for transactions with external inputs: in addition to the existing warning and external outputs, the trusted screen now shows the total amount of the external inputs when it can be reliably determined, and the net amount spent from or received into the account.
- Standard BIP-87 xpubs can now be exported without explicit user confirmation.
+- Enabled stack protector.
## [2.4.6] - 30-03-2026
Why 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.