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
113
114
115
116
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <tier.nolan@gmail.com>) id 1We0pj-0007Kw-1w
for bitcoin-development@lists.sourceforge.net;
Sat, 26 Apr 2014 11:31:51 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.216.54 as permitted sender)
client-ip=209.85.216.54; envelope-from=tier.nolan@gmail.com;
helo=mail-qa0-f54.google.com;
Received: from mail-qa0-f54.google.com ([209.85.216.54])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1We0pi-00066Q-AK
for bitcoin-development@lists.sourceforge.net;
Sat, 26 Apr 2014 11:31:51 +0000
Received: by mail-qa0-f54.google.com with SMTP id w8so4665019qac.27
for <bitcoin-development@lists.sourceforge.net>;
Sat, 26 Apr 2014 04:31:44 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.229.112.5 with SMTP id u5mr18873976qcp.3.1398511904865; Sat,
26 Apr 2014 04:31:44 -0700 (PDT)
Received: by 10.140.25.86 with HTTP; Sat, 26 Apr 2014 04:31:44 -0700 (PDT)
In-Reply-To: <CAC1+kJMJOB+OSkL1ZZ_DpGBnYoNPVX7eNR_=adqF6rMaM-LKSA@mail.gmail.com>
References: <CAE-z3OVsQAya3RDzMTvKNK4hLGQVjFOp6Bseo=xK4ApOdPCh8g@mail.gmail.com>
<CAE28kUT4rZJHzww5gsdkCyzyKV6q2bV4h4rL_hzAcvhtCpKW4w@mail.gmail.com>
<20140425201403.GA8994@savin>
<CAAS2fgQc_UgwYgc0kVso-cL6xqP-2MGg2JoWDHYyAUXhQkyaoA@mail.gmail.com>
<20140425211426.GD8994@savin>
<CAE-z3OUM6_+qtxzcLg1FkUe8jxCLnJDya=eH9O5+LY_KRrhZpg@mail.gmail.com>
<CAC1+kJMJOB+OSkL1ZZ_DpGBnYoNPVX7eNR_=adqF6rMaM-LKSA@mail.gmail.com>
Date: Sat, 26 Apr 2014 12:31:44 +0100
Message-ID: <CAE-z3OXmsK2WLSxzHjbvPUdpKSE2J_nVXkWF=J_9+ijruV-U4w@mail.gmail.com>
From: Tier Nolan <tier.nolan@gmail.com>
To: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=001a11330a744dc3fe04f7f06d84
X-Spam-Score: -0.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
(tier.nolan[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-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: 1We0pi-00066Q-AK
Subject: Re: [Bitcoin-development] BIP - Hash Locked Transaction
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: Sat, 26 Apr 2014 11:31:51 -0000
--001a11330a744dc3fe04f7f06d84
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
On Sat, Apr 26, 2014 at 12:11 PM, Jorge Tim=C3=B3n <jtimon@monetize.io> wro=
te:
> script IsStandard
> main IsStandardTx
> main AcceptToMemoryPool
>
Accept to memory pool could probably be replaced with an
IsStandard(scriptPubKey, scriptSig) method. The only "isStandard" part of
the process is the check inputs method (and AcceptToMemoryPool calls
IsStandardTx).
The standard script methods at the moment are also used for extracting
addresses for wallet management.
The standard script check could be made easier if it just checked for
pattern matches.
Is there any objections to this change, other than it doesn't go far enough=
?
--001a11330a744dc3fe04f7f06d84
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div><div><div>On Sat, Apr 26, 2014 at 12:11 PM, Jorge Tim=
=C3=B3n <span dir=3D"ltr"><<a href=3D"mailto:jtimon@monetize.io" target=
=3D"_blank">jtimon@monetize.io</a>></span> wrote:<br><div class=3D"gmail=
_extra"><div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
script IsStandard<br>
main IsStandardTx<br>
main AcceptToMemoryPool<br>
</blockquote></div><br></div>Accept to memory pool could probably be replac=
ed with an IsStandard(scriptPubKey, scriptSig) method.=C2=A0 The only "=
;isStandard" part of the process is the check inputs method (and Accep=
tToMemoryPool calls IsStandardTx).<br>
<br></div>The standard script methods at the moment are also used for extra=
cting addresses for wallet management.<br><br></div>The standard script che=
ck could be made easier if it just checked for pattern matches.<br><br>
</div><div>Is there any objections to this change, other than it doesn'=
t go far enough?<br></div></div>
--001a11330a744dc3fe04f7f06d84--
|
