FD
← All projectsFoundation

Passport firmware

Firmware for Foundation Passport Bitcoin signing devices.

BitcoinHardware walletsNormal
Repository coverage

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

102security candidates79second-pass queue215AI analyses
42commits · 30 days
128commits · 60 days
194commits · 180 days
256commits · 365 days
Backfill bands
Aug 5 → Feb 612 seen0 candidatesComplete
Feb 6 → Jun 659 seen3 candidatesComplete
Jun 6 → Jul 64 seen0 candidatesComplete
Jul 6 → Aug 52 seen0 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.

61/100 average clarity
16Strong · 80–100
116Adequate · 60–79
118Thin · 40–59
13Opaque · 0–39
4security 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.
Jacksper13321424466
Matt Gleason841868351
Jack603454261
mjg-foundation693251269
Jean-Pierre De Jesus DIAZ828061
Ken Carpenter313048
QnA111060
dependabot[bot]505076
BitcoinQnA101045
Analysis record

Published AI watches

Last scanned 48 minutes ago

Informational 12 AI analysisMessage 78 · Adequate
FD FoundationPassport firmware BitcoinHardware wallets

SFT-8696: remove the Security Check from onboarding

This commit removes the 'Security Check' step from the initial device setup (onboarding) for the Passport hardware wallet. To avoid breaking devices that were mid-setup during a firmware update, the old step is kept as a harmless pass-thro…

8d77ba38by Jack+153−124 files
No security note in commit
Low 37 AI analysisMessage 73 · Adequate
FD FoundationPassport firmware BitcoinHardware wallets

Merge pull request #753 from Foundation-Devices/sft-8680-fail-to-sign-dynamic-taproot-qr-message

This commit adds support for signing BIP-322 message requests that wallets like Sparrow send as a PSBT (a Bitcoin transaction-like data format). It is a feature addition, not a reported vulnerability fix. The code includes careful validati…

New input parser for externally supplied PSBT data with explicit structural validationRejects non-Taproot BIP-322 requests and unsafe sighash typesBinds the user-reviewed message and address to the transaction being signed
5e98b6abby mjg-foundation+722−3011 files
No security note in commit
Moderate 59 AI analysisMessage 50 · Thin
FD FoundationPassport firmware BitcoinHardware wallets

SFT-8680: check derivation path length before indexing into it

This commit fixes a bug in the Passport hardware wallet's BIP-322 message signing code. Previously, when parsing a PSBT (a Bitcoin data format), the code could read past the end of an empty or too-short 'derivation path' field because it c…

Out-of-bounds read / index error on untrusted PSBT inputValidation order bug: first-byte check before length checkBIP-322 signing request parsing hardened
cec3925bby Matt Gleason+8−43 files
No security note in commit
Informational 22 AI analysisMessage 73 · Adequate
FD FoundationPassport firmware BitcoinHardware wallets

Merge pull request #754 from Foundation-Devices/sft-8681-passport-core-sign-taproot-messages-with

This commit changes how the Passport hardware wallet signs Bitcoin Taproot text messages. Previously it used SIGHASH_DEFAULT (the Taproot default), but now it uses SIGHASH_ALL. The change is for compatibility: the commit message says Sparr…

Change in cryptographic signature hash type (SIGHASH_DEFAULT -> SIGHASH_ALL)Comment explicitly references verifier compatibility and Sparrow wallet acceptanceUnit test asserts new signature encoding and verifies against an external test vector
87f43de1by mjg-foundation+22−172 files
No security note in commit
Low 41 AI analysisMessage 73 · Adequate
FD FoundationPassport firmware BitcoinHardware wallets

Merge pull request #752 from Foundation-Devices/sft-8674-passport-core-signing-flow-does-not-show-a-non

This commit adds on-screen warnings to the Passport hardware wallet when a user is reviewing a Bitcoin transaction that contains timelocks. Timelocks can prevent a transaction from confirming until a future date or until certain inputs hav…

UI warning for absolute time-based nLockTimeUI warning for BIP68 relative timelocks on version-2 transactionsHeight-based nLockTime intentionally not flagged to avoid false positives
5defe2c5by mjg-foundation+176−16 files
No security note in commit
Moderate 52 AI analysisMessage 85 · Strong
FD FoundationPassport firmware BitcoinHardware wallets

SFT-8674: warned about timelocks when reviewing a transaction

This commit adds on-screen warnings to the Passport hardware wallet when a Bitcoin transaction being reviewed includes a timelock that could delay confirmation. Before this change, a user could unknowingly sign a transaction that is blocke…

UI now warns users about transaction timelocks that delay confirmationPreviously undisclosed to the signer: absolute date locks and BIP68 relative locksHeight-based nLockTime intentionally not flagged to avoid warning fatigue
7cba5349by Jack+176−16 files
Vendor flagged security relevance
Moderate 59 AI analysisMessage 73 · Adequate
FD FoundationPassport firmware BitcoinHardware wallets

Merge pull request #747 from Foundation-Devices/sft-8653-passport-core-recheck-the-firmware-image-while

This update tightens the firmware update process on the Passport hardware wallet. Previously, the device verified the firmware file once, then copied it to internal flash memory without re-checking. A malicious or tampered file swapped in …

Time-of-check/time-of-use (TOCTOU) hardening in firmware update pathNew digest parameter threaded from verification task to staging taskStaging task now re-hashes firmware image and compares against expected digest
3449381fby mjg-foundation+68−264 files
No security note in commit
Moderate 60 AI analysisMessage 58 · Thin
FD FoundationPassport firmware BitcoinHardware wallets

Merge pull request #736 from Foundation-Devices/sft-8554-bootloader-setup-checks

This commit hardens how Passport's bootloader handles a sensitive factory key during initial device setup. Previously, the code trusted that erasing the key from SPI flash succeeded without checking, and it left a temporary copy of the key…

Sensitive key material (supply-chain validation key) is now explicitly zeroed from stack memory after useSPI flash erase of the SCV key is now verified by read-back instead of assumed successfulBootloader setup now aborts if the SCV key cannot be confirmed erased from SPI flash
ed62d448by mjg-foundation+245−55 files
No security note in commit
Moderate 62 AI analysisMessage 73 · Adequate
FD FoundationPassport firmware BitcoinHardware wallets

Merge pull request #735 from Foundation-Devices/sft-8555-update-restore-checks

This commit adds security checks when restoring a backup file to a Passport hardware wallet. Previously, multisig wallet configurations stored in a backup were restored without verifying that they actually belong to the seed being restored…

Validation of multisig backup records against restored seedDerivation verification for xpubs claiming backup root fingerprintDropping malformed records instead of failing entire restore
8dbae7e1by mjg-foundation+242−75 files
Vendor flagged security relevance
Moderate 60 AI analysisMessage 73 · Adequate
FD FoundationPassport firmware BitcoinHardware wallets

Merge pull request #748 from Foundation-Devices/sft-8654-passport-core-bounded-text-building-in-the

This commit replaces unsafe string-copying functions in the Passport hardware wallet's bootloader with a bounded helper that prevents text fields from overflowing their buffers. The change is defensive: it stops malicious or malformed firm…

Replacement of strcpy/strcat with bounded append_text helperHandling of non-NUL-terminated firmware header text fieldsBuffer overflow mitigation in bootloader UI message construction
e2d735f0by mjg-foundation+89−222 files
No security note in commit
Informational 15 AI analysisMessage 73 · Adequate
FD FoundationPassport firmware BitcoinHardware wallets

Merge pull request #732 from Foundation-Devices/sft-8545-native-taproot-key-signing

This commit adds a new, dedicated way for the Passport hardware wallet to sign Bitcoin Taproot transactions. It moves the cryptographic 'tweak' calculation from Python code into a Rust library and adds unit tests. There is nothing in the c…

5e3ed701by mjg-foundation+234−185 files
No security note in commit
Moderate 60 AI analysisMessage 73 · Adequate
FD FoundationPassport firmware BitcoinHardware wallets

Merge pull request #742 from Foundation-Devices/sft-8530-distinct-cosigners

This update to the Passport hardware wallet firmware adds a safety check when importing multi-signature wallet configurations. Previously, the same cosigner public key could be listed more than once under different fingerprints or address …

Adds duplicate-key detection during multisig wallet importCompares raw public-key x-coordinates rather than fingerprints or encoded xpub stringsPrevents a single key from being counted as multiple independent cosigners
92c68c63by mjg-foundation+69−03 files
Vendor flagged security relevance
Low 48 AI analysisMessage 73 · Adequate
FD FoundationPassport firmware BitcoinHardware wallets

Merge pull request #739 from Foundation-Devices/sft-8559-psbt-file-errors

This update fixes a bug where the Passport hardware wallet could freeze (hang) when reading a malformed or unreadable PSBT transaction file from a microSD card. Now the device reports a clear error instead of getting stuck, so users know s…

Denial-of-service / UI hang on malformed input now returns an errorUnhandled exception path now caught and reported instead of leaving task unresolvedMissing microSD card case explicitly reported
6a461136by mjg-foundation+144−62 files
No security note in commit
Low 34 AI analysisMessage 73 · Adequate
FD FoundationPassport firmware BitcoinHardware wallets

Merge pull request #740 from Foundation-Devices/sft-4482-update-card-missing

This commit fixes a user-experience bug in the Passport hardware wallet's firmware update flow. Previously, if the user removed the microSD card while the device was reading a firmware update file, the process would crash with an unhandled…

Adds exception handling for a removable-media failure during a privileged operation (firmware update)Prevents unhandled CardMissingError from aborting the update flow abruptlyDoes not alter firmware signature, timestamp, or header validation logic
06ec8d6aby mjg-foundation+109−23 files
No security note in commit
Moderate 59 AI analysisMessage 73 · Adequate
FD FoundationPassport firmware BitcoinHardware wallets

Merge pull request #741 from Foundation-Devices/sft-737-multisig-match-n

This firmware update fixes a bug in how the Passport hardware wallet matches multisignature (multisig) wallets. Previously, when looking for a saved wallet that matches the cosigners in a transaction, the device only checked that the cosig…

Incorrect multisig wallet matching could lead to signing with the wrong wallet policySubset-only cosigner matching allowed a smaller wallet to be conflated with a larger oneFix adds N filter to wallet candidate enumeration
d2d30a58by mjg-foundation+59−23 files
No security note in commit
Informational 15 AI analysisMessage 73 · Adequate
FD FoundationPassport firmware BitcoinHardware wallets

Merge pull request #746 from Foundation-Devices/sft-8260-evaluate-miniscript-no-compatible-path

This commit only changes the wording of an on-screen warning message shown to users when a Bitcoin transaction's timelock conditions are not yet met. It does not change any security logic, validation, or behavior. The old message said no s…

f6ab63ceby Jacksper13+5−42 files
No security note in commit
Informational 15 AI analysisMessage 73 · Adequate
FD FoundationPassport firmware BitcoinHardware wallets

SFT-8260: Update the policy no-compatible-path warning copy

This commit only changes the wording of an on-screen warning message shown to users when a Bitcoin transaction cannot be signed because no spending path's time-lock conditions are currently satisfied. It does not change any security logic,…

e024471eby Jack+5−42 files
No security note in commit
Informational 21 AI analysisMessage 58 · Thin
FD FoundationPassport firmware BitcoinHardware wallets

Merge pull request #731 from Foundation-Devices/SFT-974-miniscript-ui-followup

This commit is a follow-up to the miniscript wallet-policy user interface. It mostly fixes UI wording, memory cleanup, and policy display logic. The only potentially security-relevant change is that wallet policy IDs are now computed with …

Incremental SHA-256 digest used for policy ID computationRemoval of explicit `validate(miniscript, context)` call before compilationNew default-name derivation from descriptor checksum
83d1d576by mjg-foundation+415−5312 files
No security note in commit
Low 32 AI analysisMessage 50 · Thin
FD FoundationPassport firmware BitcoinHardware wallets

SFT-974: unwrapped miniscript parsing recursion, added default policy

This firmware update changes how the Passport hardware wallet handles complex Bitcoin wallet policies. The main visible change is replacing a recursive parser walk with an iterative one, which prevents the device from crashing due to exces…

Recursion in miniscript parsing replaced with explicit stack to avoid RecursionError on deeply nested templatesPolicy validation path changed: explicit `validate()` call removed, safety now enforced via `compile_miniscript()` during registrationDefault empty policy name now auto-populated from descriptor checksum to avoid unnamed policies
96b2aa9fby Matt Gleason+160−216 files
No security note in commit
Informational 20 AI analysisMessage 50 · Thin
FD FoundationPassport firmware BitcoinHardware wallets

SFT-974: improved miniscript UI, working on OOM issues

This commit is a routine feature and stability patch for the Passport hardware wallet's miniscript wallet-policy support. It improves on-screen descriptions of wallet policies, adds explicit memory cleanup (garbage collection) during polic…

Memory pressure mitigation via explicit garbage collection during policy operationsNew verify-address flow for registered wallet policiesUI clarity improvements for timelock and signer-role descriptions
cb7478a5by Matt Gleason+255−3210 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.

Security candidateSFT-8696: remove the Security Check from onboardingby Jack · 8d77ba38 · Nov 18, 2026 · 4 filesMessage 78 · AdequateInformational 12Details
Commit message · Jack

SFT-8696: remove the Security Check from onboarding

Both setup flows now go from the step before the Security Check
straight to setting the PIN.

Onboarding saves its progress by step name, and throws all of it away
when a saved name no longer exists. A new unit usually updates its
firmware during onboarding, so the progress it restores after the update
names the Security Check step. Deleting the step would send that unit
back to the start of onboarding with its PIN already set. The step stays
as a pass-through instead: entered going forward, it continues to the
PIN; entered going back, it returns to the step before it.

78/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Names security-relevant behavior explicitly
Why it was queued
access control
AI analysis · Informational 12/100

This commit removes the 'Security Check' step from the initial device setup (onboarding) for the Passport hardware wallet. To avoid breaking devices that were mid-setup during a firmware update, the old step is kept as a harmless pass-through rather than being deleted entirely. There is no indication this change fixes a security vulnerability; it is a user-experience and compatibility change.

Security candidateMerge pull request #753 from Foundation-Devices/sft-8680-fail-to-sign-dynamic-taproot-qr-messageby mjg-foundation · 5e98b6ab · Nov 17, 2026 · 11 filesMessage 73 · AdequateLow 37Details
Commit message · mjg-foundation

Merge pull request #753 from Foundation-Devices/sft-8680-fail-to-sign-dynamic-taproot-qr-message

SFT-8680: sign BIP-322 message requests sent as a PSBT

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
signing boundarycryptography-sensitive pathsigning or wallet pathmerge-commit duplicate discount
AI analysis · Low 37/100

This commit adds support for signing BIP-322 message requests that wallets like Sparrow send as a PSBT (a Bitcoin transaction-like data format). It is a feature addition, not a reported vulnerability fix. The code includes careful validation: it checks the message matches the transaction, the address is Taproot, the derivation path is correct, and the signature hash type is safe. There is no direct evidence in the commit that this fixes an active security bug, but it does reduce the risk of a user being tricked into signing the wrong message or signing for the wrong address.

Security candidateSFT-8680: check derivation path length before indexing into itby Matt Gleason · cec3925b · Nov 17, 2026 · 3 filesMessage 50 · ThinModerate 59Details
Commit message · Matt Gleason

SFT-8680: check derivation path length before indexing into it

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 59/100

This commit fixes a bug in the Passport hardware wallet's BIP-322 message signing code. Previously, when parsing a PSBT (a Bitcoin data format), the code could read past the end of an empty or too-short 'derivation path' field because it checked the first byte before confirming the field was long enough. The fix reorders the checks so the length is validated before any byte is accessed. This prevents a potential crash or undefined behavior when handling a malformed signing request.

Security candidateMerge pull request #754 from Foundation-Devices/sft-8681-passport-core-sign-taproot-messages-withby mjg-foundation · 87f43de1 · Nov 17, 2026 · 2 filesMessage 73 · AdequateInformational 22Details
Commit message · mjg-foundation

Merge pull request #754 from Foundation-Devices/sft-8681-passport-core-sign-taproot-messages-with

SFT-8681: sign Taproot messages with SIGHASH_ALL

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
cryptography-sensitive pathmerge-commit duplicate discount
AI analysis · Informational 22/100

This commit changes how the Passport hardware wallet signs Bitcoin Taproot text messages. Previously it used SIGHASH_DEFAULT (the Taproot default), but now it uses SIGHASH_ALL. The change is for compatibility: the commit message says Sparrow wallet only accepts SIGHASH_ALL for these signatures. This is a standards-compliance and interoperability fix, not a security vulnerability fix. The included tests were updated to expect the new signature format.

Security candidateMerge pull request #752 from Foundation-Devices/sft-8674-passport-core-signing-flow-does-not-show-a-nonby mjg-foundation · 5defe2c5 · Nov 17, 2026 · 6 filesMessage 73 · AdequateLow 41Details
Commit message · mjg-foundation

Merge pull request #752 from Foundation-Devices/sft-8674-passport-core-signing-flow-does-not-show-a-non

SFT-8674: warn about timelocks when reviewing a transaction

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
signing boundarysigning or wallet pathmerge-commit duplicate discount
AI analysis · Low 41/100

This commit adds on-screen warnings to the Passport hardware wallet when a user is reviewing a Bitcoin transaction that contains timelocks. Timelocks can prevent a transaction from confirming until a future date or until certain inputs have aged, which could be used to trick someone into signing a payment that cannot actually be spent right away. The change does not alter transaction validation rules; it only makes existing timelock behavior visible to the user during signing.

AI review queuedSFT-8674: warned about timelocks when reviewing a transactionby Jack · 7cba5349 · Nov 16, 2026 · 6 filesMessage 85 · StrongModerate 52Details
Commit message · Jack

SFT-8674: warned about timelocks when reviewing a transaction

A transaction can be signed with a lock that stops it confirming until
a date, or until its inputs have aged, and the review never showed
either. The amounts can't change, but the payment can be held up
without the signer knowing.

Only those two cases are flagged. Most wallets set nLockTime to the
current block height on every transaction to deter fee sniping, and
Passport doesn't know the current height, so a height lock can't be
told apart from one far in the future. Flagging every height would put
a warning on almost every transaction.

The date is computed directly because utime counts from 2000 on this
port, so utils.timestamp_to_str would be 30 years off for a Unix time.

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Moderate 52/100

This commit adds on-screen warnings to the Passport hardware wallet when a Bitcoin transaction being reviewed includes a timelock that could delay confirmation. Before this change, a user could unknowingly sign a transaction that is blocked from confirming until a future date or until its inputs have aged. The amounts cannot change, but the payment can be held up. The fix flags only date-based and relative timelocks, not the common anti-fee-sniping block-height locks that most wallets set.

Security candidateMerge pull request #747 from Foundation-Devices/sft-8653-passport-core-recheck-the-firmware-image-whileby mjg-foundation · 3449381f · Nov 12, 2026 · 4 filesMessage 73 · AdequateModerate 59Details
Commit message · mjg-foundation

Merge pull request #747 from Foundation-Devices/sft-8653-passport-core-recheck-the-firmware-image-while

SFT-8653: recheck the firmware image while staging an update

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
signing or wallet pathboot or update pathmerge-commit duplicate discount
AI analysis · Moderate 59/100

This update tightens the firmware update process on the Passport hardware wallet. Previously, the device verified the firmware file once, then copied it to internal flash memory without re-checking. A malicious or tampered file swapped in between those two steps could potentially be installed. The patch now computes a fingerprint (a SHA-256 hash) during the first verification and re-computes it while staging the update, refusing to proceed if the file has changed. This is a defensive hardening change rather than a confirmed exploit fix.

Security candidateMerge pull request #736 from Foundation-Devices/sft-8554-bootloader-setup-checksby mjg-foundation · ed62d448 · Nov 11, 2026 · 5 filesMessage 58 · ThinModerate 60Details
Commit message · mjg-foundation

Merge pull request #736 from Foundation-Devices/sft-8554-bootloader-setup-checks

SFT-8554: bootloader setup tidy-ups

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
update trustboot or update pathmerge-commit duplicate discount
AI analysis · Moderate 60/100

This commit hardens how Passport's bootloader handles a sensitive factory key during initial device setup. Previously, the code trusted that erasing the key from SPI flash succeeded without checking, and it left a temporary copy of the key sitting in memory after use. The patch now verifies the key is actually gone from flash, retries the erase if needed, and wipes the temporary memory copy immediately. It also adds automated tests that simulate failures to make sure the key is never left behind.

AI review queuedMerge pull request #735 from Foundation-Devices/sft-8555-update-restore-checksby mjg-foundation · 8dbae7e1 · Nov 11, 2026 · 5 filesMessage 73 · AdequateModerate 62Details
Commit message · mjg-foundation

Merge pull request #735 from Foundation-Devices/sft-8555-update-restore-checks

SFT-8555: check multisig configs when restoring a backup

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
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Moderate 62/100

This commit adds security checks when restoring a backup file to a Passport hardware wallet. Previously, multisig wallet configurations stored in a backup were restored without verifying that they actually belong to the seed being restored. The new code validates each multisig configuration: it checks that the structure is correct, that the keys are valid, and that any key claiming to belong to the restored seed really derives from it. Bad multisig records are now dropped instead of causing the entire restore to fail, so the seed is still recovered and the user can re-import a valid multisig config later. This prevents a malicious or corrupted backup from sneaking a fake multisig wallet onto the device.

Security candidateMerge pull request #748 from Foundation-Devices/sft-8654-passport-core-bounded-text-building-in-theby mjg-foundation · e2d735f0 · Nov 11, 2026 · 2 filesMessage 73 · AdequateModerate 60Details
Commit message · mjg-foundation

Merge pull request #748 from Foundation-Devices/sft-8654-passport-core-bounded-text-building-in-the

SFT-8654: bounded text building in the bootloader

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
update trustboot or update pathmerge-commit duplicate discount
AI analysis · Moderate 60/100

This commit replaces unsafe string-copying functions in the Passport hardware wallet's bootloader with a bounded helper that prevents text fields from overflowing their buffers. The change is defensive: it stops malicious or malformed firmware headers (whose version/date fields are not guaranteed to end with a NUL byte) from causing buffer overflows when the bootloader displays information or asks the user to approve a firmware recovery.

Security candidateMerge pull request #732 from Foundation-Devices/sft-8545-native-taproot-key-signingby mjg-foundation · 5e3ed701 · Nov 10, 2026 · 5 filesMessage 73 · AdequateInformational 15Details
Commit message · mjg-foundation

Merge pull request #732 from Foundation-Devices/sft-8545-native-taproot-key-signing

SFT-8545: sign Taproot key path spends in one native call

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
signing boundarycryptography-sensitive pathsigning or wallet pathmerge-commit duplicate discount
AI analysis · Informational 15/100

This commit adds a new, dedicated way for the Passport hardware wallet to sign Bitcoin Taproot transactions. It moves the cryptographic 'tweak' calculation from Python code into a Rust library and adds unit tests. There is nothing in the commit message or code changes that suggests a security bug was fixed; it reads as a normal feature/refactoring improvement.

AI review queuedMerge pull request #742 from Foundation-Devices/sft-8530-distinct-cosignersby mjg-foundation · 92c68c63 · Nov 10, 2026 · 3 filesMessage 73 · AdequateModerate 60Details
Commit message · mjg-foundation

Merge pull request #742 from Foundation-Devices/sft-8530-distinct-cosigners

SFT-8530: require distinct cosigner keys on multisig import

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
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Moderate 60/100

This update to the Passport hardware wallet firmware adds a safety check when importing multi-signature wallet configurations. Previously, the same cosigner public key could be listed more than once under different fingerprints or address formats. Now the device rejects duplicate cosigner keys, preventing a user from being tricked into thinking they have an independent cosigner when they actually do not. This is a security hardening fix for a logic flaw in multisig import validation.

Security candidateMerge pull request #739 from Foundation-Devices/sft-8559-psbt-file-errorsby mjg-foundation · 6a461136 · Nov 10, 2026 · 2 filesMessage 73 · AdequateLow 48Details
Commit message · mjg-foundation

Merge pull request #739 from Foundation-Devices/sft-8559-psbt-file-errors

SFT-8559: report unreadable PSBT files instead of hanging

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
signing boundarysigning or wallet pathmerge-commit duplicate discount
AI analysis · Low 48/100

This update fixes a bug where the Passport hardware wallet could freeze (hang) when reading a malformed or unreadable PSBT transaction file from a microSD card. Now the device reports a clear error instead of getting stuck, so users know something went wrong and can try again.

Security candidateMerge pull request #740 from Foundation-Devices/sft-4482-update-card-missingby mjg-foundation · 06ec8d6a · Nov 10, 2026 · 3 filesMessage 73 · AdequateLow 34Details
Commit message · mjg-foundation

Merge pull request #740 from Foundation-Devices/sft-4482-update-card-missing

SFT-4482: handle a missing card while checking a firmware update

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
boot or update pathmerge-commit duplicate discount
AI analysis · Low 34/100

This commit fixes a user-experience bug in the Passport hardware wallet's firmware update flow. Previously, if the user removed the microSD card while the device was reading a firmware update file, the process would crash with an unhandled error. Now the device detects the missing card, prompts the user to reinsert it, and only gives up if the user declines. It also adds a friendly error message if the file becomes unreadable for other reasons. There is no direct evidence this was exploitable to install malicious firmware or steal funds.

AI review queuedMerge pull request #741 from Foundation-Devices/sft-737-multisig-match-nby mjg-foundation · d2d30a58 · Nov 10, 2026 · 3 filesMessage 73 · AdequateModerate 59Details
Commit message · mjg-foundation

Merge pull request #741 from Foundation-Devices/sft-737-multisig-match-n

SFT-737: match multisig wallets on N as well as cosigners

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
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Moderate 59/100

This firmware update fixes a bug in how the Passport hardware wallet matches multisignature (multisig) wallets. Previously, when looking for a saved wallet that matches the cosigners in a transaction, the device only checked that the cosigners overlapped. This meant a smaller wallet (for example, one needing 2 signatures out of 2 people) could be mistaken for a larger wallet (for example, 2 signatures out of 3 people) if the larger wallet contained the same people. The fix now also checks that the total number of cosigners (N) matches, so a smaller wallet is correctly treated as a separate wallet. The commit adds a test showing that a 2-of-2 wallet is no longer confused with a 2-of-3 wallet that shares two cosigners.

AI review queuedMerge pull request #746 from Foundation-Devices/sft-8260-evaluate-miniscript-no-compatible-pathby Jacksper13 · f6ab63ce · Nov 9, 2026 · 2 filesMessage 73 · AdequateInformational 15Details
Commit message · Jacksper13

Merge pull request #746 from Foundation-Devices/sft-8260-evaluate-miniscript-no-compatible-path

SFT-8260: update the policy no-compatible-path warning copy

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
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit only changes the wording of an on-screen warning message shown to users when a Bitcoin transaction's timelock conditions are not yet met. It does not change any security logic, validation, or behavior. The old message said no spending path was compatible with the transaction; the new message explains more precisely that the transaction fails a timelock and will be rejected by the network. A corresponding test was updated to expect the new text.

AI review queuedSFT-8260: Update the policy no-compatible-path warning copyby Jack · e024471e · Nov 9, 2026 · 2 filesMessage 73 · AdequateInformational 15Details
Commit message · Jack

SFT-8260: Update the policy no-compatible-path warning copy

Name the cause (no spending path's timelock is met), say the network
will reject the transaction, and tell the user to rebuild it.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit only changes the wording of an on-screen warning message shown to users when a Bitcoin transaction cannot be signed because no spending path's time-lock conditions are currently satisfied. It does not change any security logic, validation, or behavior. The old and new messages describe the same situation; the new text is clearer and more accurately explains that the network would reject the transaction.

AI review queuedMerge pull request #731 from Foundation-Devices/SFT-974-miniscript-ui-followupby mjg-foundation · 83d1d576 · Nov 4, 2026 · 12 filesMessage 58 · ThinInformational 21Details
Commit message · mjg-foundation

Merge pull request #731 from Foundation-Devices/SFT-974-miniscript-ui-followup

SFT-974: miniscript UI followup

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
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 21/100

This commit is a follow-up to the miniscript wallet-policy user interface. It mostly fixes UI wording, memory cleanup, and policy display logic. The only potentially security-relevant change is that wallet policy IDs are now computed with an incremental SHA-256 digest instead of a single buffer, and a few validation steps were removed or reordered. There is no direct evidence of an exploitable vulnerability in the diff, but the change is large enough that a subtle bug could hide in the new policy import/backup flows.

AI review queuedSFT-974: unwrapped miniscript parsing recursion, added default policyby Matt Gleason · 96b2aa9f · Nov 1, 2026 · 6 filesMessage 50 · ThinLow 32Details
Commit message · Matt Gleason

SFT-974: unwrapped miniscript parsing recursion, added default policy
names

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 32/100

This firmware update changes how the Passport hardware wallet handles complex Bitcoin wallet policies. The main visible change is replacing a recursive parser walk with an iterative one, which prevents the device from crashing due to excessive recursion on deeply nested policies. It also adds automatic default names for imported policies and tweaks the import flow so users without external signers skip an unnecessary step. There is no direct evidence in the commit that this fixes an exploitable security vulnerability; it appears to be a robustness and usability improvement.

AI review queuedSFT-974: improved miniscript UI, working on OOM issuesby Matt Gleason · cb7478a5 · Oct 27, 2026 · 10 filesMessage 50 · ThinInformational 20Details
Commit message · Matt Gleason

SFT-974: improved miniscript UI, working on OOM issues

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 20/100

This commit is a routine feature and stability patch for the Passport hardware wallet's miniscript wallet-policy support. It improves on-screen descriptions of wallet policies, adds explicit memory cleanup (garbage collection) during policy import/export to avoid out-of-memory crashes, and replaces a 'Verify Liana Address' menu item with a generic 'Verify Address' flow. There is no direct evidence in the commit of a security vulnerability being fixed; the changes are framed by the vendor as user-interface and memory-management improvements.

Security candidateMerge pull request #728 from Foundation-Devices/SFT-3834-message-signing-microsd-lengthby mjg-foundation · 8409c279 · Oct 27, 2026 · 14 filesMessage 73 · AdequateLow 44Details
Commit message · mjg-foundation

Merge pull request #728 from Foundation-Devices/SFT-3834-message-signing-microsd-length

SFT-3834: restored newline support in messages being signed, increased

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
signing boundarysigning or wallet pathmerge-commit duplicate discount
AI analysis · Low 44/100

This firmware update changes how the Passport hardware wallet handles message signing. It restores the ability to sign messages containing newlines (which had been blocked), increases the maximum microSD message file size from 240 to 4096 bytes, and adds a warning when a message ends in invisible whitespace. The core risk is that invisible characters at the end of a message, or a very long message that the user cannot fully review, could lead someone to sign something different from what they think they saw. The patch adds safeguards (footer warning, forced scrolling to the end) rather than removing all restrictions.

Security candidateSFT-3834: preserved trailing newlines and added a warning for signingby Matt Gleason · 305577a9 · Oct 27, 2026 · 6 filesMessage 50 · ThinLow 40Details
Commit message · Matt Gleason

SFT-3834: preserved trailing newlines and added a warning for signing
them

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing boundarysigning or wallet path
AI analysis · Low 40/100

This commit changes how the Passport hardware wallet displays messages before the user signs them. It now keeps trailing newlines and spaces exactly as they appear in the original message, instead of trimming them, and shows a warning when a message ends with such invisible characters. The goal is to prevent a trick where an attacker hides part of a message after many blank lines so the user only sees the harmless-looking top portion and unknowingly signs something different.

Security candidateMerge pull request #729 from Foundation-Devices/sft-8489-dependabot-pillow-gif-seek-keeps-rejected-size-afterby mjg-foundation · 3cf83f54 · Oct 27, 2026 · 7 filesMessage 73 · AdequateLow 34Details
Commit message · mjg-foundation

Merge pull request #729 from Foundation-Devices/sft-8489-dependabot-pillow-gif-seek-keeps-rejected-size-after

SFT-8489: move host tooling and the simulator to Pillow 13.0.0

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
boot or update pathautomated dependency-update discountmerge-commit duplicate discount
AI analysis · Low 34/100

This commit updates the Passport firmware project's host-side tooling and simulator to use Pillow 13.0.0 instead of Pillow 12.3.x. The change is explicitly described as fixing open Pillow security advisories that are resolved in 13.0.0. It also fixes a small simulator bug where screen buffer reads could request more data than needed. The changes affect only developer/host tooling and the simulator, not the actual Passport hardware firmware.

Security candidateSFT-8489: move host tooling and the simulator to Pillow 13.0.0by Jack · 36571f0e · Oct 26, 2026 · 6 filesMessage 73 · AdequateLow 38Details
Commit message · Jack

SFT-8489: move host tooling and the simulator to Pillow 13.0.0

Every open Pillow Dependabot alert (seven advisories, each reported against
both extmod/trezor-firmware/pyproject.toml and
python/requirements-optional.txt) is fixed in 13.0.0. The constraints
allowed 12.3.0 up to but excluding 13.

Pillow 13 requires Python 3.11, so the version floor and the Python marker
move together; a floor on its own would leave no installable Pillow on
3.10. setup.py's extra and DEVELOPMENT.md get the same change, and
simulator/requirements.txt gains a floor.

The simulator's dev shell takes Pillow from nixpkgs, which still ships
12.3.0. Override it in the Python package set with 13.0.0 from the PyPI
sdist, so imageio resolves to the same copy as the shell. nixpkgs' build
recipe applies unchanged.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
boot or update pathautomated dependency-update discount
AI analysis · Low 38/100

This commit updates the Pillow image-processing library used by developer tools and the firmware simulator from version 12.3.x to 13.0.0. The change fixes seven known security advisories reported by Dependabot. Pillow is not part of the actual Passport hardware wallet firmware that protects private keys; it is only used on developers' computers and in the simulator. The commit also raises the minimum Python version from 3.10 to 3.11 and adjusts the project's Nix package setup to provide Pillow 13.0.0.

AI review queuedMerge pull request #727 from Foundation-Devices/SFT-8316-show-op-return-payloads-containing-null-as-hexby mjg-foundation · 53fd6c15 · Oct 23, 2026 · 2 filesMessage 73 · AdequateLow 41Details
Commit message · mjg-foundation

Merge pull request #727 from Foundation-Devices/SFT-8316-show-op-return-payloads-containing-null-as-hex

SFT-8316: prevented null truncation in op_return messages

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
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Low 41/100

This update fixes a display issue on the Passport hardware wallet when showing Bitcoin OP_RETURN message data. Previously, if the message contained a null (zero-value) byte, the on-screen text would be cut off at that point, hiding anything after it. The device now shows the full message as hexadecimal instead. This matters because a user approving a transaction might only see part of an embedded message, which could be used to mislead them about what the transaction actually contains.