summaryrefslogtreecommitdiff
path: root/26/137cdb096384bf3812772e2645cb07bed05111
blob: 754f126866281c7a98a28c86fa360b979ee25da6 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <sipa@ulyssis.org>) id 1RsB84-000363-LA
	for bitcoin-development@lists.sourceforge.net;
	Tue, 31 Jan 2012 10:40:00 +0000
X-ACL-Warn: 
Received: from rhcavuit02.kulnet.kuleuven.be ([134.58.240.130]
	helo=cavuit02.kulnet.kuleuven.be)
	by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
	id 1RsB7y-0006bY-O0 for bitcoin-development@lists.sourceforge.net;
	Tue, 31 Jan 2012 10:40:00 +0000
X-KULeuven-Envelope-From: sipa@ulyssis.org
X-Spam-Status: not spam, SpamAssassin (not cached, score=-48.797, required 5, 
	autolearn=disabled, DKIM_ADSP_CUSTOM_MED 0.00, FAKE_REPLY_C 0.00,
	FREEMAIL_FROM 0.00, KUL_SMTPS -50.00, NML_ADSP_CUSTOM_MED 1.20)
X-KULeuven-Scanned: Found to be clean
X-KULeuven-ID: A87CB12802B.A7604
X-KULeuven-Information: Katholieke Universiteit Leuven
Received: from smtps02.kuleuven.be (smtpshost02.kulnet.kuleuven.be
	[134.58.240.75])
	by cavuit02.kulnet.kuleuven.be (Postfix) with ESMTP id A87CB12802B
	for <bitcoin-development@lists.sourceforge.net>;
	Tue, 31 Jan 2012 11:39:44 +0100 (CET)
Received: from smtp.ulyssis.org (mail.ulyssis.student.kuleuven.be
	[193.190.253.235])
	by smtps02.kuleuven.be (Postfix) with ESMTP id B14C5F3862
	for <bitcoin-development@lists.sourceforge.net>;
	Tue, 31 Jan 2012 11:39:44 +0100 (CET)
Received: from wop.ulyssis.org (wop.intern.ulyssis.org [192.168.0.182])
	by smtp.ulyssis.org (Postfix) with ESMTP id 7803410052
	for <bitcoin-development@lists.sourceforge.net>;
	Tue, 31 Jan 2012 11:41:05 +0100 (CET)
Received: by wop.ulyssis.org (Postfix, from userid 615)
	id 8FF7F87C1AB; Tue, 31 Jan 2012 11:39:44 +0100 (CET)
Date: Tue, 31 Jan 2012 11:39:44 +0100
X-Kuleuven: This mail passed the K.U.Leuven mailcluster
From: Pieter Wuille <pieter.wuille@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Message-ID: <20120131103943.GA31329@ulyssis.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-PGP-Key: http://sipa.ulyssis.org/pubkey.asc
User-Agent: Mutt/1.5.20 (2009-06-14)
X-Spam-Score: 1.2 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(pieter.wuille[at]gmail.com)
	0.0 DKIM_ADSP_CUSTOM_MED   No valid author signature, adsp_override is
	CUSTOM_MED 0.0 FAKE_REPLY_C           FAKE_REPLY_C
	1.2 NML_ADSP_CUSTOM_MED    ADSP custom_med hit,
	and not from a mailing list
	-0.0 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1RsB7y-0006bY-O0
Subject: Re: [Bitcoin-development] BIP 21 (modification BIP 20)]
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Tue, 31 Jan 2012 10:40:00 -0000

On Tue, Jan 31, 2012 at 09:35:26AM +0100, Wladimir wrote:
> I also wonder whether the "send to private address" should be part of this
> BIP, or a future one.

It is actually a "send of private key", not to. And I agree, it should be part
of a separate BIP.

-- 
Pieter