mirror of
https://github.com/bitcoin/bips.git
synced 2025-05-12 12:03:29 +00:00
Clarify handling of duplicated keys
This commit is contained in:
parent
bfae1799d3
commit
45df424759
@ -260,10 +260,9 @@ pass those key-value pairs through when re-serializing the transaction.
|
|||||||
|
|
||||||
===Handling Duplicated Keys===
|
===Handling Duplicated Keys===
|
||||||
|
|
||||||
Keys within each scope should never be duplicated; all keys in the format are unique. However implementors
|
Keys within each scope should never be duplicated; all keys in the format are unique. PSBTs containing duplicate keys are invalid. However implementors
|
||||||
will still need to handle events where keys are duplicated, either duplicated in the transaction
|
will still need to handle events where keys are duplicated when combining transactions with duplicated fields. In this event, the software may choose
|
||||||
itself or when combining transactions with duplicated fields. If duplicated keys are
|
whichever value it wishes.
|
||||||
encountered, the software may choose to use any of the values corresponding to that key.
|
|
||||||
|
|
||||||
==Responsibilities==
|
==Responsibilities==
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user