LD
← All projectsLedger

Ledger Bitcoin app

Open-source Bitcoin application running on Ledger devices; the device OS is outside this repository.

BitcoinHardware walletsNormal
Repository coverage

447 commits in the local evidence base

Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.

148security candidates154second-pass queue402AI analyses
19commits · 30 days
63commits · 60 days
249commits · 180 days
414commits · 365 days
Backfill bands
Aug 5 → Feb 670 seen8 candidatesComplete
Feb 6 → Jun 6149 seen21 candidatesComplete
Jun 6 → Jul 623 seen0 candidatesComplete
Jul 6 → Aug 555 seen5 candidatesComplete
Commit communication

Does the history explain itself?

Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.

57/100 average clarity
50Strong · 80–100
152Adequate · 60–79
186Thin · 40–59
59Opaque · 0–39
6security candidates with opaque commit messaging
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
Salvatore Ingala2981122561062
Ilya Artemov962696145
Ruben Waterman666083
Aymeric Robert434063
github-actions[bot]17117046
Mathias BROUSSET17015039
José Luis Landabaso Díaz404067
iartemov-ledger201051
Cerberus Merlin101062
Michael Evans101073
Charles-Edouard de la Vergne101045
Analysis record

Published AI watches

Last scanned 24 minutes ago

Informational 20 AI analysisMessage 83 · Strong
LD LedgerLedger Bitcoin app BitcoinHardware wallets

tests: pin all Python test dependencies to exact versions

This commit pins the exact versions of Python testing tools used by the project's automated tests. Previously, the test setup allowed any newly released version of those tools to be installed automatically, which could introduce unexpected…

Supply-chain risk reduction for test/CI dependenciesPrevents unreviewed automatic upgrades of speculos and raggerNo change to firmware or published package code
def417a3by Salvatore Ingala+329−142 files
No security note in commit
Informational 15 AI analysisMessage 38 · Opaque
LD LedgerLedger Bitcoin app BitcoinHardware wallets

Bump version to 2.6.0

This commit is a routine version bump from 2.5.1 to 2.6.0 in the Ledger Bitcoin app. It only updates the version number in the Makefile and the release date in the CHANGELOG. There are no code changes, no bug fixes, and no security-related…

2b424b54by Salvatore Ingala+4−42 files
No security note in commit
Moderate 66 AI analysisMessage 68 · Adequate
LD LedgerLedger Bitcoin app BitcoinHardware wallets

Merge pull request #581 from LedgerHQ/client-fixes

This commit tightens how the Ledger Bitcoin app and its companion client libraries read PSBT (Partially Signed Bitcoin Transaction) data. It adds checks that reject malformed or suspicious PSBTs: truncated fields, unexpected extra bytes af…

Hardened PSBT deserialization against truncation and trailing dataAdded duplicate-key detection in PSBT mapsRejected PSBTv2-only fields inside PSBTv0 to prevent locktime/field override attacks
f8f790a3by Salvatore Ingala+544−17018 files
No security note in commit
Low 47 AI analysisMessage 73 · Adequate
LD LedgerLedger Bitcoin app BitcoinHardware wallets

python client: reject PSBTv2-only fields in a PSBTv0

This commit tightens input validation in the Python helper library that prepares Bitcoin transaction data for Ledger hardware wallets. It now rejects PSBT files that claim to be the older version 0 format but contain fields that only belon…

Input-validation hardening: stricter parsing of PSBT version 0 to reject v2-only key typesConsistency fix across clients: aligns Python client with HS and Rust client behaviorLocktime normalization during v0-to-v2 conversion to prevent per-input locktime from overriding transaction locktime
84165be7by Salvatore Ingala+92−02 files
No security note in commit
Informational 24 AI analysisMessage 83 · Strong
LD LedgerLedger Bitcoin app BitcoinHardware wallets

tests: update authproxy.py to the latest version from Bitcoin Core

This commit updates a test helper file used to talk to a Bitcoin node during automated testing. The old helper could accidentally send the same command twice if the network connection hiccuped, which could cause a test-only action like sen…

Removed transparent retry of non-idempotent RPC requests after connection resetsTest helper could execute state-changing RPCs twice before the fixNew connection-per-call configuration mitigates idle-timeout disconnects without retry risk
c7ca508eby Salvatore Ingala+91−522 files
Vendor flagged security relevance
Low 40 AI analysisMessage 65 · Adequate
LD LedgerLedger Bitcoin app BitcoinHardware wallets

Reject duplicate keys and trailing data when parsing a PSBT in the JS client

This commit fixes the JavaScript PSBT (Partially Signed Bitcoin Transaction) parser in Ledger's Bitcoin app so it now rejects malformed PSBTs that contain duplicate keys or extra trailing bytes. Previously, such malformed data could be acc…

BIP-174 non-compliance: duplicate keys and trailing data were previously acceptedState reuse bug: deserializing multiple PSBTs in the same instance could merge mapsInput validation gap in client-side PSBT parsing
4942a4aeby Salvatore Ingala+40−02 files
No security note in commit
Informational 15 AI analysisMessage 73 · Adequate
LD LedgerLedger Bitcoin app BitcoinHardware wallets

ragger: fail if a request succeeds without showing the expected screens

This commit fixes the automated test harness, not the Ledger Bitcoin app itself. Previously, the test framework could silently pass even when the device completed a request without showing the expected on-screen review. The change makes te…

Test-hardening only: no firmware or runtime application code changedFixes false-negative test results where a request could succeed without expected UI reviewCorrects scope of navigation settings to avoid leaking across nested or subsequent calls
202d352aby Salvatore Ingala+76−957 files
No security note in commit
Low 37 AI analysisMessage 88 · Strong
LD LedgerLedger Bitcoin app BitcoinHardware wallets

unit tests: Fix length overflow in unit-test PSBT parser

This commit fixes an arithmetic overflow bug in a test-only PSBT (Bitcoin transaction format) parser used in unit tests. The bug could let a crafted test input make the parser think a data length is huge, potentially confusing the mock dis…

Integer overflow/wrap-around in length calculationOut-of-bounds length derived from arithmetic on attacker-influenced offsetsUnit-test-only code path, not device firmware
6a2a9262by Salvatore Ingala+6−21 file
No security note in commit
Low 48 AI analysisMessage 73 · Adequate
LD LedgerLedger Bitcoin app BitcoinHardware wallets

rust client: reject PSBTv2-only fields when converting a PSBTv0

This commit fixes a bug in the Ledger Bitcoin app's Rust client where a PSBT v0 (an older transaction format) could silently carry fields that only have meaning in PSBT v2. When converting v0 to v2, those fields could override values taken…

Input validation added for cross-format PSBT conversionPrevents v2-only fields from overriding unsigned-transaction-derived valuesBIP-370 compliance enforcement for PSBTv0
602055d6by Salvatore Ingala+66−91 file
No security note in commit
Moderate 51 AI analysisMessage 73 · Adequate
LD LedgerLedger Bitcoin app BitcoinHardware wallets

Reject PSBTv2-only fields when converting a PSBTv0 in the JS client

This commit fixes a bug in the Ledger Bitcoin app's JavaScript client library. When converting an older-style Bitcoin transaction file (PSBT version 0) into the newer PSBT version 2 format, the library previously ignored fields that are on…

Input validation fix: rejects malformed PSBTv0 containing v2-only fieldsPrevents silent override of transaction locktime during PSBTv0-to-v2 conversionAdds missing BIP-370 key type constants for required time/height locktime
a1f6dc84by Salvatore Ingala+66−22 files
No security note in commit
High 72 AI analysisMessage 73 · Adequate
LD LedgerLedger Bitcoin app BitcoinHardware wallets

Reject duplicate keys and truncated maps when parsing PSBT maps in sign_psbt

This commit fixes a bug in how the Ledger Bitcoin app client parses PSBT (Partially Signed Bitcoin Transaction) maps. Previously, if the same key appeared twice in a map, the parser silently kept the last value. A malicious or malformed PS…

Silent overwrite of duplicate PSBT map keys could create commitment mismatch between client and deviceTruncated PSBT maps were silently accepted due to exception swallowing in deserialization loopsTrailing data after PSBT maps was ignored, allowing reserialization to silently normalize malformed inputs
75df80f9by Salvatore Ingala+107−104 files
Vendor flagged security relevance
High 72 AI analysisMessage 53 · Thin
LD LedgerLedger Bitcoin app BitcoinHardware wallets

Merge pull request #579 from LedgerHQ/misc-fixes

This commit fixes several bugs in Ledger's Bitcoin app. The most serious ones are: (1) a set of miniscript policy analyzer mistakes that could let the app accept Bitcoin wallet policies whose scripts are too large or too expensive to execu…

Miniscript cost/property analysis errors that could allow oversized/undercosted wallet policiesHost-driven infinite-loop / denial-of-service via zero-length GET_MORE_ELEMENTS responsesUI state inconsistency causing a security warning to be prematurely dismissed
ec389348by Salvatore Ingala+413−3113 files
No security note in commit
Low 26 AI analysisMessage 73 · Adequate
LD LedgerLedger Bitcoin app BitcoinHardware wallets

Merge pull request #576 from LedgerHQ/musig2_improvements

This commit improves the Ledger Bitcoin app's MuSig2 multi-signature feature. It lets wallet software pre-generate public nonces before a transaction is known, adds an optional MUSIG2_SESSION_ID field so multiple signing sessions can be in…

New PSBT proprietary field parsing with length validation (1-32 bytes, empty rejected)Session ID now commits to wallet policy plus optional MUSIG2_SESSION_IDSession storage limit raised from 8 to 32 with LRU eviction
26d22adcby Salvatore Ingala+710−7216 files
No security note in commit
Informational 18 AI analysisMessage 85 · Strong
LD LedgerLedger Bitcoin app BitcoinHardware wallets

Use signed scratch arrays in the thresh ops and stack size computations

This commit is a small code cleanup in Ledger's Bitcoin app. It changes two local arrays from unsigned (uint16_t) to signed (int16_t) in functions that count operations and stack sizes for Bitcoin miniscript 'thresh' policies. The commit m…

Signed/unsigned type mismatch in sentinel handlingPotential latent integer interpretation bug in miniscript threshold policy analysisCode clarity improvement around invalid (dis)satisfaction markers
4ff6f2f0by Salvatore Ingala+4−41 file
No security note in commit
Low 48 AI analysisMessage 91 · Strong
LD LedgerLedger Bitcoin app BitcoinHardware wallets

Align miniscript type and ops computations with bitcoin-core

This commit fixes the Ledger Bitcoin app's internal checker for Miniscript wallet policies. The checker was incorrectly rejecting some valid Bitcoin spending policies as unsafe, and in a few places it was computing safety properties using …

Logic change in Miniscript policy analysisAlignment with upstream Bitcoin Core reference implementationRelaxation of overly strict non-malleability and timelock-mixing checks
4694d317by Salvatore Ingala+26−132 files
No security note in commit
Moderate 68 AI analysisMessage 86 · Strong
LD LedgerLedger Bitcoin app BitcoinHardware wallets

Fix ops computation for andor fragments

This commit fixes a bug in how the Ledger Bitcoin app counts the number of Bitcoin script operations (ops) needed to spend certain wallet policies that use a 'miniscript andor' fragment. Because the count was wrong, the app could allow use…

Incorrect miniscript ops accounting for andor fragmentPolicy sanity check bypass leading to unspendable registered walletsReference alignment with Bitcoin Core implementation
86159d1eby Salvatore Ingala+40−13 files
Vendor flagged security relevance
High 74 AI analysisMessage 78 · Adequate
LD LedgerLedger Bitcoin app BitcoinHardware wallets

Fix ops computation for l: and u: fragments

This commit fixes a bug in how the Ledger Bitcoin app counts Bitcoin script operations ('ops') for two specific Miniscript fragments, 'l:' and 'u:'. Because the count was too low, the app could accept wallet policies that look valid but ar…

Undercounting of script operation budget leading to acceptance of unspendable policiesIncorrect handling of Miniscript wrapper dissatisfaction semanticsPolicy sanity check bypass via operation-count accounting flaw
b6ac1de8by Salvatore Ingala+39−33 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 68 · Adequate
LD LedgerLedger Bitcoin app BitcoinHardware wallets

doc: document the MUSIG2_SESSION_ID PSBT field

This commit only updates documentation and the changelog. It explains a new optional PSBT field called MUSIG2_SESSION_ID that lets software wallets manage multiple MuSig2 signing sessions for the same wallet policy on a Ledger device. Ther…

8d8ed9afby Salvatore Ingala+28−62 files
No security note in commit
Informational 15 AI analysisMessage 78 · Adequate
LD LedgerLedger Bitcoin app BitcoinHardware wallets

musig_sessions: store up to 32 sessions

This commit is a simple capacity increase, not a security fix. It raises the number of simultaneous MuSig2 signing sessions the Ledger Bitcoin app can keep in memory from 8 to 32, because users with multiple MuSig accounts or wallets that …

a6798172by Salvatore Ingala+12−54 files
No security note in commit
Low 26 AI analysisMessage 73 · Adequate
LD LedgerLedger Bitcoin app BitcoinHardware wallets

sign_psbt: fail before the UI if the MuSig2 session is missing

This commit improves the user experience and error handling for Ledger's Bitcoin app when using MuSig2 multi-signatures. Previously, if a required MuSig2 session was missing during the second round of signing, the device would only report …

UX-hardening: fail-fast before user approval instead of afterNew specific error code EC_SIGN_PSBT_MUSIG2_SESSION_NOT_FOUND for missing MuSig2 sessionsRefactored session storage lookup to support non-destructive existence check
2d04b144by Salvatore Ingala+118−187 files
No security note in commit
Repository ledger

Explore captured commits

Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.

Lower-priorityAdding few more tests including for Electrum and BIP-45 pathsby Ilya Artemov · 16dc0eff · Dec 15, 2025 · 1 fileMessage 60 · AdequateInformational 12Details
Commit message · Ilya Artemov

Adding few more tests including for Electrum and BIP-45 paths

60/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
AI analysis · Informational 12/100

This commit only adds and updates automated tests for the Ledger Bitcoin app's extended public key feature. It does not change any application code, cryptographic logic, or security behavior. The tests verify that certain Bitcoin derivation paths (including Electrum and BIP-45 style paths) are accepted or rejected as expected. There is no indication of a security fix or vulnerability being patched.

Lower-priorityAdding exception for Electrum walletby Ilya Artemov · 9afe3e96 · Dec 15, 2025 · 1 fileMessage 45 · ThinLow 25Details
Commit message · Ilya Artemov

Adding exception for Electrum wallet

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Low 25/100

This commit changes the Ledger Bitcoin app's Makefile to add two extra allowed derivation paths alongside the standard Bitcoin paths. One path (4541509') appears to be a special Electrum wallet path, and the other (45') is the BIP-45 whole-tree path for multi-signature wallets. This is a configuration change that widens which key derivation paths the app can use, but it does not by itself look like a vulnerability fix or an exploit. It is more like a compatibility/permission update.

Lower-priorityMake the JS client accept the 'Bitcoin Recovery' appby Salvatore Ingala · 926a3209 · Dec 12, 2025 · 1 fileMessage 50 · ThinInformational 21Details
Commit message · Salvatore Ingala

Make the JS client accept the 'Bitcoin Recovery' app

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 21/100

This commit updates the JavaScript client for Ledger's Bitcoin app so it also recognizes an app named 'Bitcoin Recovery' as the main Bitcoin network app. Previously, only 'Bitcoin' and 'Bitcoin Test' were accepted. This is a small compatibility change and does not appear to be a security fix.

Lower-priorityBump version of JS client library to 2.3.0by Salvatore Ingala · 47bac89e · Dec 12, 2025 · 4 filesMessage 45 · ThinInformational 15Details
Commit message · Salvatore Ingala

Bump version of JS client library to 2.3.0

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 15/100

This commit is a routine packaging update for the JavaScript client library of Ledger's Bitcoin app. It bumps the version number, refreshes the package-lock.json dependency manifest, and makes two tiny configuration cleanups (removing an unused word from the spell-check dictionary and a redundant Prettier ESLint preset). There are no code changes that handle user data, cryptographic operations, or device communication, and nothing in the commit describes a security fix or vulnerability.

Lower-priorityRe-enabling test_get_extended_pubkey_non_standard for Speculos as now it is hardened thereby Ilya Artemov · 48189643 · Dec 11, 2025 · 1 fileMessage 50 · ThinInformational 17Details
Commit message · Ilya Artemov

Re-enabling test_get_extended_pubkey_non_standard for Speculos as now it is hardened there

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
defensive validation
AI analysis · Informational 17/100

This commit only changes a test file. It re-enables a previously skipped automated test for the Speculos simulator because the simulator now correctly blocks an insecure key-derivation operation that the real Ledger hardware already blocked. It also adds a comment explaining another test case. There is no change to the actual app code that users run on their devices.

Lower-priorityAdding COIN=bitcoin_recovery with all the paths permittedby Ilya Artemov · 19704263 · Dec 11, 2025 · 1 fileMessage 50 · ThinLow 42Details
Commit message · Ilya Artemov

Adding COIN=bitcoin_recovery with all the paths permitted

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Low 42/100

This commit adds a new build variant called 'bitcoin_recovery' to the Ledger Bitcoin app. Unlike the normal Bitcoin app, this variant allows all BIP32 derivation paths and is intended for recovery scenarios. The commit itself does not change runtime code; it only adds a Makefile option to compile a special recovery version of the app. Because it permits all paths, if this variant were loaded onto a device and used normally, it could weaken the usual path-restriction protections, but the commit explicitly frames it as a recovery tool and blocks the dangerous AUTOAPPROVE_FOR_PERF_TESTS flag for this variant.

AI review queuedFix JS-testsby Ilya Artemov · af826a1f · Dec 8, 2025 · 1 fileMessage 38 · OpaqueInformational 15Details
Commit message · Ilya Artemov

Fix JS-tests

38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit updates a single test automation JSON file used in JavaScript tests. It changes a regular expression that matches on-screen text during automated device testing, replacing the keyword 'Key' with 'Our' and 'Their'. This is a test-only adjustment with no effect on the actual Ledger Bitcoin app firmware or its security.

AI review queued[auto-update] Update Ragger snapshotsby github-actions[bot] · e1b82eb1 · Dec 8, 2025 · 276 filesMessage 45 · ThinInformational 15Details
Commit message · github-actions[bot]

[auto-update] Update Ragger snapshots

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: unusually broad changesecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit only updates screenshot files used for automated testing of the Ledger Bitcoin app. No application code, firmware, or user-facing behavior was changed. It is not a security fix and does not introduce a vulnerability.

Lower-priorityRearranging the key information so it fits without ...by Ilya Artemov · 2aeafd38 · Dec 8, 2025 · 1 fileMessage 50 · ThinInformational 15Details
Commit message · Ilya Artemov

Rearranging the key information so it fits without ...

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 15/100

This commit only changes the on-screen text shown when registering a Bitcoin wallet policy on a Ledger device. It rewords labels like 'ours' to 'Our' and shortens the format so the text fits on the device's small screen. There is no security-relevant change.

Lower-priorityConverting build warnings to errorsby Ilya Artemov · 871ec9d3 · Dec 4, 2025 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · Ilya Artemov

Converting build warnings to errors

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 15/100

This commit adds a compiler flag (-Werror) that turns all build warnings into errors. It is a build-hardening change, not a fix for a specific security bug. There is no evidence in the commit of any vulnerability, exploit, or affected code path.

Lower-priorityUsing generic and simpler format_sats_amount() for swap as wellby Ilya Artemov · b200772e · Dec 4, 2025 · 3 filesMessage 50 · ThinLow 26Details
Commit message · Ilya Artemov

Using generic and simpler format_sats_amount() for swap as well

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Low 26/100

This commit replaces a custom Bitcoin amount-formatting routine used during Ledger's cryptocurrency swap feature with a shared, simpler utility. The old code converted an 8-byte big-endian amount into a human-readable decimal string with a coin ticker. The new code uses the project's generic `format_sats_amount()` function. The change removes about 120 lines of low-level bit-manipulation code. On its own, the commit does not claim to fix a security bug, and the diff does not show an obvious vulnerability. However, any change to amount display logic in a swap context is security-sensitive because a bug could mislead a user about how much value is being exchanged.

Security candidateAdditional check to avoid vout_scriptpubkey overflowby Ilya Artemov · aeeeaf09 · Dec 4, 2025 · 1 fileMessage 67 · AdequateHigh 71Details
Commit message · Ilya Artemov

Additional check to avoid vout_scriptpubkey overflow

67/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Explains rationale or failure mode✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
memory safetysigning or wallet path
AI analysis · High 71/100

This commit adds a safety check in the Ledger Bitcoin app's code that parses previous transaction outputs. Before copying a scriptPubKey (the part of a Bitcoin output that locks funds) into a fixed-size buffer, the code now verifies the copy won't exceed the buffer's maximum length when combined with how much has already been written. Without this check, a malformed or oversized scriptPubKey could overflow the buffer, potentially corrupting memory and affecting the device's behavior. The commit also fixes two nearby variables from 'bool' to 'int' so parser error codes are preserved instead of being collapsed to true/false.

Lower-priorityUpdate CHANGELOG.mdby iartemov-ledger · 5506c97d · Nov 25, 2025 · 1 fileMessage 43 · ThinInformational 15Details
Commit message · iartemov-ledger

Update CHANGELOG.md

Co-authored-by: Salvatore Ingala <6681844+bigspider@users.noreply.github.com>

43/100 · ThinMessage clarity
✓ Subject identifies a change✓ Provides an explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100

This commit only edits the project's CHANGELOG.md file, removing an empty '### Added' heading and merging its bullet points into the preceding release section. There are no code changes, no functional changes, and no security fixes or features introduced.

Lower-priority[auto-update] Update Ragger snapshotsby github-actions[bot] · f9b860c2 · Nov 25, 2025 · 3 filesMessage 45 · ThinInformational 15Details
Commit message · github-actions[bot]

[auto-update] Update Ragger snapshots

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 15/100

This commit only updates three test snapshot images used by an automated testing tool called Ragger. These snapshots are reference screenshots of device screens during tests. There are no code changes, no application logic changes, and nothing that affects the security of the Bitcoin app running on Ledger devices.

Lower-priorityVersion bump to v2.4.3 + changelog updateby Ilya Artemov · d42ca717 · Nov 25, 2025 · 2 filesMessage 45 · ThinInformational 15Details
Commit message · Ilya Artemov

Version bump to v2.4.3 + changelog update

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 15/100

This commit only bumps the app version number from 2.4.2 to 2.4.3 and updates the changelog. No code changes to security logic are present in the diff. The changelog mentions prior security-related UI and derivation-path hardening work, but those changes were made in earlier commits, not here.

AI review queuedFixing unit testsby Ilya Artemov · 79f44e7a · Nov 25, 2025 · 1 fileMessage 38 · OpaqueInformational 15Details
Commit message · Ilya Artemov

Fixing unit tests

38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This commit adds a single type definition (`cx_err_t`) to a unit-test mock header so the test code compiles. It does not change any actual application code, cryptographic operations, or device behavior. There is no security relevance.

AI review queued[auto-update] Update Ragger snapshotsby github-actions[bot] · d9756e65 · Nov 25, 2025 · 50 filesMessage 45 · ThinInformational 15Details
Commit message · github-actions[bot]

[auto-update] Update Ragger snapshots

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
second-pass: unusually broad change
AI analysis · Informational 15/100

This commit only updates test screenshot images used by the Ragger testing framework. No application code, firmware logic, or user-facing behavior was changed. It is not a security patch and does not fix or introduce any vulnerability.

Security candidateSpecial handling for get_extended_pubkey_at_path() distinguishing error codesby Ilya Artemov · cf630a59 · Nov 25, 2025 · 7 filesMessage 50 · ThinLow 38Details
Commit message · Ilya Artemov

Special handling for get_extended_pubkey_at_path() distinguishing error codes

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathsigning or wallet path
AI analysis · Low 38/100

This commit changes how the Ledger Bitcoin app reports failures when deriving public keys from a BIP32 path. Previously, almost any derivation failure was reported as a generic 'bad state' error. Now, the app distinguishes between different underlying error codes, specifically mapping two SDK error codes (0x4212 and 0x4215) to a 'not supported' status word instead of 'bad state'. This is a defensive hardening change: it gives callers more accurate error information and avoids misleading 'bad state' responses for permission or policy-related derivation failures. There is no direct evidence in the commit of an exploitable vulnerability being fixed.

AI review queuedUpdating few tests that did not respect the derivation path hardeningby Ilya Artemov · 550aa545 · Nov 25, 2025 · 2 filesMessage 60 · AdequateInformational 12Details
Commit message · Ilya Artemov

Updating few tests that did not respect the derivation path hardening

60/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
defensive validationsigning or wallet pathsecond-pass: near security thresholdsecond-pass: security-sensitive path
AI analysis · Informational 12/100

This commit only changes automated test files. It updates test cases so they use correct hardened Bitcoin derivation paths and expect the app to reject non-standard or root-level key derivation requests. There is no change to the actual app code that runs on Ledger devices, so this commit does not introduce or fix a security vulnerability by itself. It appears to be a follow-up to a real security hardening in the app firmware that happened elsewhere.

Security candidateRemoving DERIVE_MASTER flag, enforcing the derivation pathsby Ilya Artemov · a4888e4f · Nov 21, 2025 · 2 filesMessage 50 · ThinModerate 61Details
Commit message · Ilya Artemov

Removing DERIVE_MASTER flag, enforcing the derivation paths

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Moderate 61/100

This commit removes a special 'derive master key' permission from the Ledger Bitcoin app and replaces direct master-key derivation with a safer OS-provided fingerprint. It also enforces BIP-44 coin-type restrictions (mainnet 0' or testnet 1') at app-load time, closing a path where the app could previously be asked to derive keys outside those intended coin types. The change is defensive: it reduces the app's privileges and makes path enforcement stricter.

Lower-priorityhandler_get_master_fingerprint through new os_perso_get_master_key_identifier syscallby Ilya Artemov · 11dcea02 · Nov 21, 2025 · 1 fileMessage 50 · ThinLow 35Details
Commit message · Ilya Artemov

handler_get_master_fingerprint through new os_perso_get_master_key_identifier syscall

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Low 35/100

This commit changes how the Bitcoin app on Ledger hardware wallets obtains the wallet's master fingerprint. Previously, the app derived the master public key and computed the fingerprint itself. Now it calls a dedicated operating-system API, os_perso_get_master_key_identifier, which returns the fingerprint directly. This is a refactoring that reduces the app's own cryptographic surface and likely improves consistency with other apps, but the commit message and diff alone do not indicate a security bug was fixed.

Security candidateFixing uninitialized variableby Ilya Artemov · 27a9c9da · Nov 20, 2025 · 1 fileMessage 35 · OpaqueLow 42Details
Commit message · Ilya Artemov

Fixing uninitialized variable

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
cryptography-sensitive path
AI analysis · Low 42/100

This commit fixes a coding bug in the Ledger Bitcoin app where a variable that tracks whether cryptographic operations succeeded was not initialized before use. Because the function is marked as unsafe for secret data (it is vulnerable to timing attacks) and is now also made private to the file, the patch both removes a potential source of incorrect error handling and limits how widely the unsafe helper can be called. The actual security impact is moderate: on its own this is a defensive fix rather than a demonstrated exploit, but uninitialized error variables can in principle lead to wrong decisions downstream if an error path is taken before the variable is set.

AI review queued[auto-update] Update Ragger snapshotsby github-actions[bot] · c74ab33d · Nov 20, 2025 · 582 filesMessage 45 · ThinInformational 15Details
Commit message · github-actions[bot]

[auto-update] Update Ragger snapshots

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: unusually broad changesecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit only updates test screenshot snapshots (PNG images) used by the Ragger automated testing framework. No application source code, firmware, or cryptographic logic was changed. It is not a security patch and does not affect users' devices or funds.

Security candidateFixing expected output array length for os_derive_bip32_with_seed_no_throw() SDK functionby Ilya Artemov · e289daf9 · Nov 20, 2025 · 1 fileMessage 50 · ThinModerate 58Details
Commit message · Ilya Artemov

Fixing expected output array length for os_derive_bip32_with_seed_no_throw() SDK function

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
secret or key materialcryptography-sensitive path
AI analysis · Moderate 58/100

This commit fixes a buffer-size mismatch in the Ledger Bitcoin app. A function that derives secret keys was being asked to write 64 bytes of output into a caller-supplied 32-byte buffer. The patch now provides a 64-byte temporary buffer and copies only the needed 32 bytes afterward, then securely wipes the temporary buffer. The original bug could have caused memory corruption or leaked key material, depending on how the SDK behaves when given an undersized buffer.

AI review queued[auto-update] Update Ragger snapshotsby github-actions[bot] · 9cc63e3d · Nov 17, 2025 · 33 filesMessage 45 · ThinInformational 15Details
Commit message · github-actions[bot]

[auto-update] Update Ragger snapshots

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: unusually broad changesecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit only updates test screenshot images used by an automated testing tool called Ragger. No actual application code, firmware, or security logic was changed. It is not a security fix and does not affect users' devices or funds.