What the developer wrote
Authored by Peter D. Gray
reword
What changed, and why it matters
This commit only changes one word in a documentation file. It rephrases a sentence about how COLDCARD handles PSBT warnings under a policy rule. There is no code change, no behavior change, and no security fix or vulnerability introduced.
No action required. This is a documentation-only rewording with no security relevance.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies docs/limitations.md, replacing ‘will be blocked by policy’ with ‘will cause the transaction to be rejected.’ This is a wording clarification in user-facing documentation. No firmware source code, build scripts, tests, or cryptographic logic was changed.
Changed components
docs/limitations.mdInspect captured patch +1 / −1
diff --git a/docs/limitations.md b/docs/limitations.md
index 54af45e..46f6da9 100644
--- a/docs/limitations.md
+++ b/docs/limitations.md
@@ -219,5 +219,5 @@ We will summarize transaction outputs as "change" back into same wallet, however
- PSBT creator must put in `nLockTime` block heights (most already do to avoid fee sniping)
- maximum of 25 whitelisted addresses can be stored
- Web2FA: any number of mobile devices can be enrolled, but all will have the same shared secret
-- any warning from the PSBT, such as huge fees, will be blocked by policy.
+- any warning from the PSBT, such as huge fees, will cause the transaction to be rejected
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.