From 1761e8a4956e25a54a4e081da4573cc293bb824c Mon Sep 17 00:00:00 2001
From: azuchi <azuchi@haw.co.jp>
Date: Sat, 28 Jan 2017 18:55:50 +0900
Subject: Remove duplication BIP69

---
 bip-0069.mediawiki | 5 -----
 1 file changed, 5 deletions(-)

(limited to 'bip-0069.mediawiki')

diff --git a/bip-0069.mediawiki b/bip-0069.mediawiki
index f262126..e9f9245 100644
--- a/bip-0069.mediawiki
+++ b/bip-0069.mediawiki
@@ -25,11 +25,6 @@ This BIP is in the public domain.
 
 ==Motivation==
 
-Currently, there is no clear standard for how wallet clients ought to order transaction inputs and outputs.
-Since wallet clients are left to their own devices to determine this ordering, they often leak information about their users’ finances.
-For example, a wallet client might naively order inputs based on when addresses were added to a wallet by the user through importing or random generation.
-Many wallets will place spending outputs first and change outputs second, leaking information about both the sender and receiver’s finances to passive blockchain observers.
-Such information should remain private not only for the benefit of consumers, but in higher order financial systems must be kept secret to prevent fraud.
 Currently, there is no clear standard for how wallet clients ought to order transaction inputs and outputs.
 Since wallet clients are left to their own devices to determine this ordering, they often leak information about their users’ finances.
 For example, a wallet client might naively order inputs based on when addresses were added to a wallet by the user through importing or random generation.
-- 
cgit v1.2.3

