blob: aa96274fe4945fe112e936e6145a9124a8bffc24 (
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
104
105
106
107
108
109
110
111
112
|
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 <andyparkins@gmail.com>) id 1RsXNd-0001NC-TY
for bitcoin-development@lists.sourceforge.net;
Wed, 01 Feb 2012 10:25:33 +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 1RsXNY-00012s-Jq
for bitcoin-development@lists.sourceforge.net;
Wed, 01 Feb 2012 10:25:33 +0000
Received: by wibhq7 with SMTP id hq7so1132317wib.34
for <bitcoin-development@lists.sourceforge.net>;
Wed, 01 Feb 2012 02:25:22 -0800 (PST)
Received: by 10.180.78.6 with SMTP id x6mr7038844wiw.18.1328091922383;
Wed, 01 Feb 2012 02:25:22 -0800 (PST)
Received: from dvr.localnet (mail.360visiontechnology.com. [92.42.121.178])
by mx.google.com with ESMTPS id ho4sm43777916wib.3.2012.02.01.02.25.20
(version=TLSv1/SSLv3 cipher=OTHER);
Wed, 01 Feb 2012 02:25:21 -0800 (PST)
From: Andy Parkins <andyparkins@gmail.com>
To: Pieter Wuille <pieter.wuille@gmail.com>
Date: Wed, 1 Feb 2012 10:25:19 +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>
<201202010948.13169.andyparkins@gmail.com>
<CAPg+sBgkEd71CUGHooymeVwGkz5axZMOck5o-nic8TM706T8OQ@mail.gmail.com>
In-Reply-To: <CAPg+sBgkEd71CUGHooymeVwGkz5axZMOck5o-nic8TM706T8OQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart1459648.xEZo2mIuf8";
protocol="application/pgp-signature"; micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-Id: <201202011025.19771.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: 1RsXNY-00012s-Jq
Cc: bitcoin-development@lists.sourceforge.net
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 10:25:34 -0000
--nextPart1459648.xEZo2mIuf8
Content-Type: Text/Plain;
charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
On 2012 February 01 Wednesday, Pieter Wuille wrote:
> > old clients won't they? They don't pass IsStandard().
>=20
> IsStandard() is for accepting transactions into the memory pool.
> Non-standard transactions are verified just fine when they are in the blo=
ck
> chain.
Ah. My misunderstanding then.
=20
> If we do a breaking change to the protocol - such as adding a new
> transaction type - ALL users must upgrade. Those who don't will see a fork
> of the chain from before the first new-style transaction. That is not the
> case now.
That makes a big difference. Thanks for the correction.
Andy
=2D-=20
Dr Andy Parkins
andyparkins@gmail.com
--nextPart1459648.xEZo2mIuf8
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)
iEYEABECAAYFAk8pEw8ACgkQwQJ9gE9xL20feQCg2lmeBbikYJkq1aKUxTFOq3qL
sJAAoIbqIlNVkHU85lOZm+wNtt+PQ22r
=NbLn
-----END PGP SIGNATURE-----
--nextPart1459648.xEZo2mIuf8--
|
