SFT-8260: Update the policy no-compatible-path warning copy
What changed, and why it matters
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.
No security action needed; this is a non-security UI copy change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff updates a user-facing string in policy_display.py and the corresponding test expectation in test_wallet_policy_flows.py. The function format_signing_pages still returns the same tuple structure and still aborts signing when filtered compatible paths are empty. No code paths, cryptographic checks, or policy validation were modified.
Changed components
ports/stm32/boards/Passport/modules/policy_display.pyports/stm32/boards/Passport/modules/tests/host/test_wallet_policy_flows.pyInspect captured patch +5 / −4
### ports/stm32/boards/Passport/modules/policy_display.py
@@ -685,8 +685,9 @@ def format_signing_pages(policy, compatible_indexes=None):
if 0 <= index < len(all_paths))
if not filtered:
return (('Wallet\n{}\n\n'
- 'At least one input has no spending path compatible with this transaction.\n\n'
- 'Signing does not make it spendable. Check the transaction in your wallet app.')
+ "This transaction doesn't meet the timelock on any spending path "
+ 'for at least one input. The network will reject it even if you sign it.\n\n'
+ 'Rebuild the transaction in your wallet app.')
.format(_escape(policy.name)),)
paths = filtered
simple = _classify_simple_inheritance(policy, paths)
### ports/stm32/boards/Passport/modules/tests/host/test_wallet_policy_flows.py
@@ -39,8 +39,8 @@ def flow_method(filename, class_name, method_name):
@pytest.mark.parametrize('compatible_sets,expected', [
([], 'could not be checked'),
- ([()], 'no spending path compatible'),
- ([(0,), ()], 'no spending path compatible'),
+ ([()], 'The network will reject it'),
+ ([(0,), ()], 'The network will reject it'),
([(0,), (1,)], 'Inputs allow different spending paths'),
([(0,), (0,)], 'Spend now (1-of-1)'),
])Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.