Drop "scope" from the two ownership-claim summary lines

"An output scope claims..." reads no better than "An output claims...".
The word is doing no work in a sentence about what the output says, and
the psbt-scope sense it borrows is not the one the reader needs there.
This commit is contained in:
kdmukai
2026-08-30 15:22:41 -05:00
parent 0d374bc7b0
commit 8574c13f39
+2 -2
View File
@@ -32,7 +32,7 @@ class PSBTVerificationError(Exception):
class PSBTOutputOwnershipClaimError(PSBTVerificationError):
"""
An output scope claims this seed's fingerprint on a key the seed does not derive.
An output claims this seed's fingerprint on a key the seed does not derive.
This is asserting that an output belongs to this seed when it does not. We treat this
deception as an attack.
@@ -42,7 +42,7 @@ class PSBTOutputOwnershipClaimError(PSBTVerificationError):
class PSBTInputOwnershipClaimError(PSBTVerificationError):
"""
An input scope claims this seed's fingerprint on a key the seed does not derive.
An input claims this seed's fingerprint on a key the seed does not derive.
The same type of false claim as the output case above, but a forged input claim simply
renders the psbt unsignable (embit re-derives the real key and will refuse to sign on