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.

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.

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.

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.

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.

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.

AI review queuedSFT-8316: prevented null truncation in op_return messagesby Matt Gleason · 7bd78ead · Oct 23, 2026 · 2 filesMessage 50 · ThinLow 49Details
Commit message · Matt Gleason

SFT-8316: prevented null truncation in op_return messages

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

This commit fixes a display bug in Passport's Bitcoin signing flow. When a transaction contains an OP_RETURN message with a hidden NUL (zero-value) byte, the device's screen would silently cut off everything after that byte. An attacker could craft a message that looks short or harmless on the device, while the real message the user is approving is actually longer or different. The fix now detects NUL bytes and shows the message as raw hex instead, so the full content is visible.

AI review queuedMerge pull request #726 from Foundation-Devices/sft-7086-add-screen-confirming-amount-being-sent-to-op_returnby mjg-foundation · 8be0de19 · Oct 23, 2026 · 5 filesMessage 73 · AdequateModerate 60Details
Commit message · mjg-foundation

Merge pull request #726 from Foundation-Devices/sft-7086-add-screen-confirming-amount-being-sent-to-op_return

SFT-7086: label OP_RETURN outputs and warn when they carry value

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 commit adds safety warnings and clearer labels for a special kind of Bitcoin transaction output called OP_RETURN. Any bitcoins sent to an OP_RETURN output are permanently destroyed ('burned'). Previously, the wallet showed the amount and a user message but did not clearly tell the user the money was unspendable. The change also makes sure that if the OP_RETURN message contains unusual characters the device cannot display, it shows the raw bytes in hex instead of silently appearing blank, which could hide a hidden message or trick the user.

AI review queuedSFT-7086: fix hex import and test settings for the simulatorby Jack · 7938b404 · Oct 20, 2026 · 2 filesMessage 83 · StrongInformational 19Details
Commit message · Jack

SFT-7086: fix hex import and test settings for the simulator

ubinascii has no b2a_hex; take the hexlify alias utils already exports.
The unit harness leaves common.settings unset, so the warning test
supplies defaults for current_chain() and restores them afterwards.

83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 19/100

This commit fixes two small bugs that only affect the Passport hardware wallet's software simulator and its unit tests. It swaps one way of converting bytes to hex for another already-provided alias, and it gives the test harness default settings so a warning test can run. There is no indication this changes real-device behavior or fixes a security vulnerability.

AI review queuedMerge pull request #725 from Foundation-Devices/SFT-7375-paginate-transaction-detailsby mjg-foundation · e73a1c1c · Oct 15, 2026 · 7 filesMessage 73 · AdequateLow 29Details
Commit message · mjg-foundation

Merge pull request #725 from Foundation-Devices/SFT-7375-paginate-transaction-details

SFT-7375: switched from scrolling to pagination for transaction reviews

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

This commit changes how the Passport hardware wallet displays transaction details during signing. Instead of one long scrolling screen, it now breaks the review into separate pages and requires the user to scroll to the bottom of each page before pressing forward. This is a user-interface hardening change meant to make sure people actually see all transaction details and warnings before approving. It is not a fix for a remote exploit or a cryptographic bug, but it does reduce the chance that a user accidentally approves a bad transaction because important information was hidden off-screen.

AI review queuedSFT-7375: switched from scrolling to pagination for transaction reviewsby Matt Gleason · bb6bf4f7 · Oct 13, 2026 · 7 filesMessage 50 · ThinLow 34Details
Commit message · Matt Gleason

SFT-7375: switched from scrolling to pagination for transaction reviews

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

This commit changes how the Passport hardware wallet displays transaction details during signing. Instead of showing all outputs, change, fees, and warnings in one long scrolling screen, it breaks them into separate paginated pages and requires the user to scroll each page to the bottom before pressing forward. This is a defensive UX improvement meant to ensure users actually see every output and warning before approving a Bitcoin transaction.

AI review queuedMerge pull request #677 from Foundation-Devices/SFT-974-miniscriptby mjg-foundation · 1a10714f · Oct 10, 2026 · 58 filesMessage 58 · ThinInformational 15Details
Commit message · mjg-foundation

Merge pull request #677 from Foundation-Devices/SFT-974-miniscript

SFT-974: miniscript

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: unusually broad changesecond-pass: security-sensitive path
AI analysis · Informational 15/100

This is a large feature commit that adds Miniscript wallet policy support to the Foundation Passport firmware. It introduces new modules for parsing and validating Miniscript policies, registering wallet policies via QR/microSD, deriving addresses, and signing PSBTs that use these policies. The changes also add UI flows, tests, and CI coverage. There is no indication in the commit message or diff that this is a security fix; it reads as a new feature implementation. No vulnerability is evident from the supplied materials.

AI review queuedMerge pull request #713 from Foundation-Devices/SFT-7485-update-foundation-urby mjg-foundation · 61eb519e · Oct 9, 2026 · 3 filesMessage 58 · ThinLow 49Details
Commit message · mjg-foundation

Merge pull request #713 from Foundation-Devices/SFT-7485-update-foundation-ur

SFT-7485: update foundation-ur

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

This commit updates a Rust dependency called foundation-ur from version 0.4 to 0.5 and adds a test showing that a malformed QR code fragment no longer corrupts the next valid scan. The change appears to fix a state-poisoning bug in the QR code decoder used by the Passport hardware wallet, but the actual fix is inside the external library, not visible in this diff.

AI review queuedMerge pull request #682 from Foundation-Devices/codex/sft-7352-blockstream-coreby mjg-foundation · 0059b02f · Oct 8, 2026 · 5 filesMessage 73 · AdequateInformational 15Details
Commit message · mjg-foundation

Merge pull request #682 from Foundation-Devices/codex/sft-7352-blockstream-core

SFT-7352: Add Blockstream crypto-account export

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 adds a new feature to the Passport hardware wallet: exporting a Bitcoin account in a format compatible with Blockstream's Jade wallet. It is a pure feature addition with no visible bug fix, defensive hardening, or security patch. There is no indication in the commit that it addresses a vulnerability.

AI review queuedSFT-7909: fixed lintby Matt Gleason · 74ed0598 · Oct 8, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Matt Gleason

SFT-7909: fixed lint

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 only reformats a single line of code in a test file to satisfy a code linter. It does not change what the code does, and it is not a security fix.

AI review queuedSFT-7352: align Blockstream account export metadataby Matt Gleason · ebded2a2 · Oct 6, 2026 · 2 filesMessage 50 · ThinInformational 22Details
Commit message · Matt Gleason

SFT-7352: align Blockstream account export metadata

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

This commit tweaks how the Passport hardware wallet exports a Bitcoin account to the Blockstream Jade wallet format. It changes the way the 'testnet/mainnet' coin type is encoded in the exported data so it matches what Jade's own software produces. There is no obvious security vulnerability here; it is a compatibility/alignment fix that could prevent the receiving wallet from misinterpreting the account type.

AI review queuedSFT-8212: ur type checkingby Matt Gleason · 18f2bb28 · Oct 5, 2026 · 5 filesMessage 45 · ThinLow 47Details
Commit message · Matt Gleason

SFT-8212: ur type checking

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: security-sensitive path
AI analysis · Low 47/100

This commit tightens how Passport handles QR codes when importing a multi-signature wallet configuration. Previously, the code could accept an unexpected type of Uniform Resource (UR) object and try to treat it as plain bytes, which could cause a crash or confuse the wallet import process. Now the firmware explicitly checks that the UR type is 'bytes' before unwrapping it, and the multisig import flow only allows plain QR data or bytes-type UR data. A new unit test confirms that wrong UR types are rejected with a user-facing error.

AI review queuedMerge pull request #640 from Foundation-Devices/SFT-4502-fix-p2wpkh-nested-in-p2sh-hash-change-validationby mjg-foundation · 5842b65c · Oct 5, 2026 · 7 filesMessage 73 · AdequateHigh 76Details
Commit message · mjg-foundation

Merge pull request #640 from Foundation-Devices/SFT-4502-fix-p2wpkh-nested-in-p2sh-hash-change-validation

SFT-4502: fix p2wpkh nested in p2sh hash change validation

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 · High 76/100

This firmware update fixes a bug in how Passport hardware wallets decide whether a Bitcoin transaction's 'change' output really belongs to your wallet. Before the fix, a malicious or buggy companion app could trick the device into treating a payment to an attacker's address as mere change, or into hiding a change output that doesn't match your account type. The patch tightens the checks for nested SegWit (P2SH-wrapped P2WPKH), native SegWit, Taproot, and multisig change outputs, and makes sure outputs with unusual or incomplete derivation paths stay visible for user review instead of being silently accepted as change.

AI review queuedMerge pull request #681 from Foundation-Devices/SFT-7377-harden-utxo-historyby mjg-foundation · 9447547a · Oct 5, 2026 · 11 filesMessage 58 · ThinModerate 64Details
Commit message · mjg-foundation

Merge pull request #681 from Foundation-Devices/SFT-7377-harden-utxo-history

SFT-7377: harden utxo history

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

This commit hardens how Passport remembers past Bitcoin input amounts. Previously, the device could record an unverified amount from a rejected or malicious transaction, then later compare a real transaction against that poisoned value and wrongly reject it. The fix only saves amounts after a signature succeeds, rejects duplicate inputs earlier, and adds a user menu to clear the saved amounts. It is a defensive hardening patch rather than a remote exploit fix.

AI review queuedMerge pull request #704 from Foundation-Devices/SFT-7937-warn-one-of-n-multisigby mjg-foundation · 47dbac8c · Oct 5, 2026 · 3 filesMessage 73 · AdequateInformational 20Details
Commit message · mjg-foundation

Merge pull request #704 from Foundation-Devices/SFT-7937-warn-one-of-n-multisig

SFT-7937: showed a warning when importing a 1-of-N multisig

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

This commit adds a user-interface warning when a Passport hardware wallet is used with a 1-of-N multisig wallet. In such wallets, any single cosigner can move funds without the Passport's approval, so the device now displays a notice before signing. It is a transparency/usability improvement, not a fix for a code vulnerability.

AI review queuedMerge pull request #698 from Foundation-Devices/SFT-8167-sighash-per-input-typeby mjg-foundation · a872cc7f · Oct 1, 2026 · 4 filesMessage 73 · AdequateModerate 59Details
Commit message · mjg-foundation

Merge pull request #698 from Foundation-Devices/SFT-8167-sighash-per-input-type

SFT-8167 SFT-8168: validate sighash types per input type

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

This commit tightens how the Passport hardware wallet checks the 'sighash' flag for each transaction input based on the input type (old-style, SegWit, or Taproot). It also fixes a crash where a bare assertion with no message would make signing fail silently. The change is defensive: it rejects unsupported sighash combinations earlier and makes sure the digest the device signs matches the type recorded in the signature. This reduces the chance that a malicious or malformed PSBT could trick the wallet into signing something different from what it displays.