From c60771d2299a08299a7734a697587dde2378d489 Mon Sep 17 00:00:00 2001
From: Daniel Cousens <github@dcousens.com>
Date: Fri, 21 Aug 2015 09:07:31 +1000
Subject: reword transaction outputs in-line with transaction inputs format

---
 bip-0069.mediawiki | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

(limited to 'bip-0069.mediawiki')

diff --git a/bip-0069.mediawiki b/bip-0069.mediawiki
index d600825..f3dff42 100644
--- a/bip-0069.mediawiki
+++ b/bip-0069.mediawiki
@@ -100,11 +100,11 @@ If the previous output indices match, the inputs are considered equal.
 ===Transaction Outputs===
 
 A transaction output is defined by its scriptPubKey and amount. [3]
-For sorting purposes, we will consider a scriptPubKey in its byte array representation, and a bitcoin amount in terms of their integer number of satoshis (smallest amount ordered first).
+For the sake of efficiency, amounts should be compared first for sorting, since they contain fewer bytes of information (8 bytes) compared to a standard P2PKH scriptPubKey (25 bytes). [4]
 
-For the sake of efficiency, amounts will be considered first for sorting, since they contain fewer bytes of information (8 bytes) compared to a standard P2PKH scriptPubKey (25 bytes). [4]
-When the values are tied, the scriptPubKey is then considered.
-In the event of a tie between scriptPubKeys, sorting is irrelevant since the outputs are exactly equivalent.
+Transaction output amounts (as 64-bit unsigned integers) are to be sorted in ascending order.
+In the event of two matching output amounts, the respective output scriptPubKeys (in their little-endian, byte-array form) will be compared lexicographically, in ascending order.
+If the scriptPubKeys match, the outputs are considered equal.
 
 ===Examples===
 
-- 
cgit v1.2.3

