summaryrefslogtreecommitdiff
path: root/d5/ba519ae721405b86aa79c5749747e7a8875c79
blob: 4281037608c9ac3df9f15fedc5b4dbdeb4fbecb0 (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
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <andyparkins@gmail.com>) id 1RsWne-0001KH-Ki
	for bitcoin-development@lists.sourceforge.net;
	Wed, 01 Feb 2012 09:48:22 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.212.175 as permitted sender)
	client-ip=209.85.212.175; envelope-from=andyparkins@gmail.com;
	helo=mail-wi0-f175.google.com; 
Received: from mail-wi0-f175.google.com ([209.85.212.175])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1RsWnd-0008M2-UZ
	for bitcoin-development@lists.sourceforge.net;
	Wed, 01 Feb 2012 09:48:22 +0000
Received: by wibhq7 with SMTP id hq7so1102180wib.34
	for <bitcoin-development@lists.sourceforge.net>;
	Wed, 01 Feb 2012 01:48:15 -0800 (PST)
Received: by 10.180.8.103 with SMTP id q7mr40601791wia.1.1328089695841;
	Wed, 01 Feb 2012 01:48:15 -0800 (PST)
Received: from dvr.localnet (mail.360visiontechnology.com. [92.42.121.178])
	by mx.google.com with ESMTPS id di5sm72167627wib.3.2012.02.01.01.48.14
	(version=TLSv1/SSLv3 cipher=OTHER);
	Wed, 01 Feb 2012 01:48:14 -0800 (PST)
From: Andy Parkins <andyparkins@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Date: Wed, 1 Feb 2012 09:48:13 +0000
User-Agent: KMail/1.13.6 (Linux/3.0.0-1-686-pae; KDE/4.6.3; i686; ; )
References: <201201311651.02726.andyparkins@gmail.com>
	<201201311158.50801.luke@dashjr.org>
In-Reply-To: <201201311158.50801.luke@dashjr.org>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart8260352.exK8TWir3u";
	protocol="application/pgp-signature"; micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-Id: <201202010948.13169.andyparkins@gmail.com>
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(andyparkins[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
	author's domain
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1RsWnd-0008M2-UZ
Subject: Re: [Bitcoin-development] BIP16/17 replacement
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: Wed, 01 Feb 2012 09:48:22 -0000

--nextPart8260352.exK8TWir3u
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

On 2012 January 31 Tuesday, Luke-Jr wrote:

> Both BIP 16 and 17 are backward compatible enough that people can continue
> to use the old clients with each other. An upgrade is only required to
> send to (or create/receive on) the new 3...-form addresses. That being

Is that true?  (I'm happy to be called wrong)

It doesn't seem like it to me.  The new transaction types will be rejected =
by=20
old clients won't they?  They don't pass IsStandard().


Andy

=2D-=20
Dr Andy Parkins
andyparkins@gmail.com

--nextPart8260352.exK8TWir3u
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEABECAAYFAk8pCl0ACgkQwQJ9gE9xL23/ywCguI7MQdo0YusJ0NZe/HpVzt5h
jFIAn2dtTseD9EYvd8vqn49qi4DJG/uv
=Wvm4
-----END PGP SIGNATURE-----

--nextPart8260352.exK8TWir3u--