From 45df4247594db391b72e7b2dcbb50a09b90be87b Mon Sep 17 00:00:00 2001 From: Andrew Chow Date: Tue, 26 Jun 2018 18:08:10 -0700 Subject: [PATCH] Clarify handling of duplicated keys --- bip-0174.mediawiki | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/bip-0174.mediawiki b/bip-0174.mediawiki index 5b5bfb38..71da8b74 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==