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-priorityUpdate CHANGELOG.md for release 2.4.5by Salvatore Ingala · a29cc918 · Feb 10, 2026 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · Salvatore Ingala

Update CHANGELOG.md for release 2.4.5

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100

This commit only edits the changelog text: it updates a release date and capitalizes some bullet points. No code was changed, so it cannot by itself introduce, fix, or exploit a security issue. The changelog does mention that version 2.4.5 fixes a signing bug and changes a derivation flag, but those actual code changes are not present in this diff.

Security candidateFix issues with the communication protocol when data is chunkedby Salvatore Ingala · 0586ab2f · Feb 10, 2026 · 2 filesMessage 73 · AdequateHigh 71Details
Commit message · Salvatore Ingala

Fix issues with the communication protocol when data is chunked

- get_merkle_preimage failed to update the data_ptr pointer
- fpt_der_data_callback would read corrupted data if a zero-length
chunk (or one starting with a very large varint that does not fit
in the first chunk) is received.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
cryptography-sensitive pathsigning or wallet path
AI analysis · High 71/100

This commit fixes two bugs in the Ledger Bitcoin app's data-receiving code when large messages are split into multiple chunks. One bug caused the app to hash and copy from the wrong memory location after the first chunk, potentially corrupting a cryptographic proof. The other bug could read corrupted data or behave incorrectly if an empty chunk arrived, or if a taproot PSBT field started with a very large variable-length integer. These are memory/data-integrity issues in security-critical signing code, but the commit does not state they are exploitable for theft.

Lower-priorityMerge pull request #416 from LedgerHQ/mbr/jfrog-rs-clientby Mathias BROUSSET · d906a668 · Jan 20, 2026 · 3 filesMessage 58 · ThinInformational 15Details
Commit message · Mathias BROUSSET

Merge pull request #416 from LedgerHQ/mbr/jfrog-rs-client

jfrog rs client

58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
merge-commit duplicate discount
AI analysis · Informational 15/100

This commit adds an automated GitHub Actions job to publish the Rust Bitcoin client library to a package registry (including JFrog) when a version tag is pushed. It also changes the package author metadata from an individual contributor to 'Ledger' and adds a README acknowledgement for that contributor. There are no code changes to the library itself and no apparent security implications.

Security candidateTypo fixesby Ilya Artemov · 574e3528 · Jan 20, 2026 · 2 filesMessage 0 · OpaqueInformational 15Details
Commit message · Ilya Artemov

Typo fixes

0/100 · OpaqueMessage clarity
! Very short subject! Too few words to establish purpose! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
cryptography-sensitive path
AI analysis · Informational 15/100

This commit fixes two spelling mistakes: one in the changelog ('jome' to 'home') and one in a code comment ('In te case' to 'In the case'). No program logic, security behavior, or functionality was changed.

Lower-prioritydo NOT do a github release upon new pypi deploymentby Mathias BROUSSET · d7dcb8d7 · Jan 14, 2026 · 1 fileMessage 50 · ThinInformational 15Details
Commit message · Mathias BROUSSET

do NOT do a github release upon new pypi deployment

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100

This commit changes a single setting in the project's automated CI workflow. It stops GitHub from automatically creating a new GitHub Release every time a new Python package is published to PyPI. This is a workflow/process change, not a code change affecting the app, wallet, or any security-sensitive functionality.

AI review queuedadd deployment instructionsby Mathias BROUSSET · a4503abc · Jan 14, 2026 · 1 fileMessage 35 · OpaqueInformational 15Details
Commit message · Mathias BROUSSET

add deployment instructions

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
documentation-only discountsecond-pass: opaque commit message
AI analysis · Informational 15/100

This commit only adds documentation to the README explaining how maintainers should create release tags to trigger automatic publishing of the Python, JavaScript, and Rust client packages. No code, configuration, or security behavior was changed.

Lower-prioritypublish pypi package through reusable_pypi_deployment.ymlby Mathias BROUSSET · e0332a58 · Jan 14, 2026 · 2 filesMessage 50 · ThinInformational 15Details
Commit message · Mathias BROUSSET

publish pypi package through reusable_pypi_deployment.yml

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

This commit adds a new automated GitHub Actions job that builds and publishes a Python package to PyPI whenever a Git tag starting with 'pyclient' is pushed. It is a routine CI/CD configuration change with no apparent security relevance.

AI review queuedTaking remarks into accountby Mathias BROUSSET · a35b50f2 · Jan 13, 2026 · 4 filesMessage 35 · OpaqueInformational 15Details
Commit message · Mathias BROUSSET

Taking remarks into account

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This commit is a routine packaging and publishing cleanup for the JavaScript client. It renames the npm package from 'ledger-bitcoin' to '@ledgerhq/ledger-bitcoin', updates the README and package-lock.json accordingly, and moves the JS client deployment from a separate workflow triggered on pushes to the 'develop' branch into the main CI workflow triggered only by tags starting with 'jsclient-'. There is no change to the Bitcoin app firmware, cryptographic code, or any user-facing security behavior.

Lower-prioritytargeting correct workflow reference prior to mergingby Mathias BROUSSET · 610d314f · Jan 13, 2026 · 1 fileMessage 50 · ThinInformational 15Details
Commit message · Mathias BROUSSET

targeting correct workflow reference prior to merging

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100

This commit simply changes a GitHub Actions workflow to point at the correct, stable version of a reusable deployment workflow. It is a normal repository hygiene fix with no security relevance visible in the diff.

Lower-priorityPublish package to jfrog through reusable_npm_deployment.ymlby Mathias BROUSSET · 7037e2b3 · Jan 13, 2026 · 5 filesMessage 50 · ThinInformational 19Details
Commit message · Mathias BROUSSET

Publish package to jfrog through reusable_npm_deployment.yml

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

This commit is a packaging and publishing workflow change for Ledger's Bitcoin JavaScript client. It adds a GitHub Actions workflow to publish the package to JFrog and npm, renames the package from 'ledger-bitcoin' to '@ledgerhq/ledger-bitcoin', removes ESLint tooling, and adjusts published files. There is no direct evidence of a security vulnerability in the code changes, but the workflow pins to a non-default branch of a reusable workflow ('mbr/reusable-workflow-jfrog-npm') and removes linting tools, which slightly weakens supply-chain assurance.

Lower-priority[auto-update] Update Ragger snapshotsby github-actions[bot] · cadc96f0 · Jan 8, 2026 · 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 expected outputs of UI screens during automated tests. There are no code changes, no application logic changes, and no security-relevant modifications.

AI review queued2.4.5 version bumpby Ilya Artemov · 7bb127f3 · Jan 8, 2026 · 2 filesMessage 38 · OpaqueInformational 15Details
Commit message · Ilya Artemov

2.4.5 version bump

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

This commit is a routine version bump from 2.4.4 to 2.4.5. It only updates the version number in the Makefile and adds a changelog entry describing unrelated feature and bug-fix changes. There is no code change in this commit itself, and nothing in the diff indicates a security vulnerability or security fix.

AI review queued[auto-update] Update Ragger snapshotsby github-actions[bot] · 44e2bf8c · Jan 8, 2026 · 24 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 snapshot images used by an automated testing framework called Ragger. These are reference screenshots of Ledger device screens during tests. No application code, firmware, or user-facing behavior was changed, so this has no security relevance on its own.

Lower-priorityEnabling getting xpub at L1 (test)by Ilya Artemov · d5f0fafd · Jan 8, 2026 · 1 fileMessage 55 · ThinInformational 12Details
Commit message · Ilya Artemov

Enabling getting xpub at L1 (test)

55/100 · ThinMessage clarity
✓ 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 a new automated test case to the project's test suite. It checks that the Ledger Bitcoin app can display and return an extended public key (xpub) for a specific non-standard key path when the user approves on the device screen. There is no change to the actual app code, no security fix, and no vulnerability being introduced.

Security candidateEnabling getting xpub at L1by Ilya Artemov · b52d07ff · Jan 8, 2026 · 1 fileMessage 45 · ThinLow 29Details
Commit message · Ilya Artemov

Enabling getting xpub at L1

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Low 29/100

This small code change fixes how the Bitcoin app builds extended public keys (xpubs) for the very first account level (called 'L1', meaning a BIP32 path with just one number, like m/44'). Before, the code always tried to look up a parent public key one level above the requested path. For a single-level path, there is no usable parent above it except the master key, so that lookup could fail or behave incorrectly. The patch adds a special case: when the path has exactly one element, it uses the master key's fingerprint as the parent fingerprint instead of trying to derive a non-existent parent. This is a correctness/reliability fix rather than an obvious security vulnerability, but a broken xpub could mislead wallet software about which key hierarchy it is dealing with.

Lower-priorityFixing network displayed name for recovery + small refactoringby Ilya Artemov · b40fb00f · Jan 8, 2026 · 4 filesMessage 50 · ThinInformational 18Details
Commit message · Ilya Artemov

Fixing network displayed name for recovery + small refactoring

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

This commit fixes the on-screen name shown for a special 'Bitcoin Recovery' version of the Ledger Bitcoin app and removes some old, duplicated menu code. It is a user-interface cleanup, not a fix for a vulnerability that could steal funds or keys.

Lower-priorityRe-enabling HAVE_APPLICATION_FLAG_DERIVE_MASTER for bitcoin_recovery variant to allow all derivations paths including non-hardened onesby Michael Evans · c5cc7774 · Jan 7, 2026 · 1 fileMessage 73 · AdequateLow 35Details
Commit message · Michael Evans

Re-enabling HAVE_APPLICATION_FLAG_DERIVE_MASTER for bitcoin_recovery variant to allow all derivations paths including non-hardened ones

(cherry picked from https://github.com/LedgerHQ/app-bitcoin-new/pull/408)

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
defensive validation
AI analysis · Low 35/100

This commit re-enables a build flag for a special 'bitcoin_recovery' app variant that lets it derive any key path, including non-hardened ones. The change is intentional and limited to a recovery/debug variant, not the main Bitcoin app. It is not a vulnerability by itself, but it removes a restriction on a variant that already had broad permissions, so it slightly increases the risk surface if that variant is misused or compromised.

Lower-priority[auto-update] Update Ragger snapshots (patch version bump)by github-actions[bot] · 7dd24587 · Dec 15, 2025 · 3 filesMessage 50 · ThinInformational 15Details
Commit message · github-actions[bot]

[auto-update] Update Ragger snapshots (patch version bump)

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 updates three test snapshot images used by the Ragger testing framework. These are reference screenshots for automated UI tests on Ledger hardware device simulators. No application code, firmware logic, or security-sensitive files were changed.

AI review queuedPatch version bumpby Ilya Artemov · 8907740c · Dec 15, 2025 · 2 filesMessage 28 · OpaqueInformational 15Details
Commit message · Ilya Artemov

Patch version bump

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

This commit is a routine version bump from 2.4.3 to 2.4.4. It only updates the version number in the Makefile and adds a changelog entry describing two newly allowed Bitcoin derivation paths. There are no code changes in the diff, so it does not introduce, fix, or alter any security-relevant behavior on its own.

AI review queued[auto-update] Update Ragger snapshotsby github-actions[bot] · 40acd185 · Dec 15, 2025 · 24 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 an automated testing tool called Ragger. No application code, firmware, or user-facing behavior was changed. It has no security relevance on its own.

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-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-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-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.