diff options
| author | Andrew Chow <achow101-github@achow101.com> | 2018-06-26 18:08:10 -0700 |
|---|---|---|
| committer | Andrew Chow <achow101-github@achow101.com> | 2018-07-05 15:27:41 -0700 |
| commit | 45df4247594db391b72e7b2dcbb50a09b90be87b (patch) | |
| tree | c14bf4873596d84d8bf149dca2a756df0492b488 /bip-0174.mediawiki | |
| parent | bfae1799d3ac8e8c118f0d9ff762dd6fefc91fe2 (diff) | |
| download | bips-45df4247594db391b72e7b2dcbb50a09b90be87b.tar.xz | |
Clarify handling of duplicated keys
Diffstat (limited to 'bip-0174.mediawiki')
| -rw-r--r-- | bip-0174.mediawiki | 7 |
1 files changed, 3 insertions, 4 deletions
diff --git a/bip-0174.mediawiki b/bip-0174.mediawiki index 5b5bfb3..71da8b7 100644 --- a/bip-0174.mediawiki +++ b/bip-0174.mediawiki @@ -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== |