mirror of
https://github.com/bitcoin/bips.git
synced 2024-11-19 01:40:05 +01: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===
|
||||
|
||||
Keys within each scope should never be duplicated; all keys in the format are unique. However implementors
|
||||
will still need to handle events where keys are duplicated, either duplicated in the transaction
|
||||
itself or when combining transactions with duplicated fields. If duplicated keys are
|
||||
encountered, the software may choose to use any of the values corresponding to that key.
|
||||
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 when combining transactions with duplicated fields. In this event, the software may choose
|
||||
whichever value it wishes.
|
||||
|
||||
==Responsibilities==
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user