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
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <tier.nolan@gmail.com>) id 1Wdn3L-00081L-1p
for bitcoin-development@lists.sourceforge.net;
Fri, 25 Apr 2014 20:48:59 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.216.182 as permitted sender)
client-ip=209.85.216.182; envelope-from=tier.nolan@gmail.com;
helo=mail-qc0-f182.google.com;
Received: from mail-qc0-f182.google.com ([209.85.216.182])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Wdn3K-00069z-0b
for bitcoin-development@lists.sourceforge.net;
Fri, 25 Apr 2014 20:48:59 +0000
Received: by mail-qc0-f182.google.com with SMTP id e16so4637725qcx.27
for <bitcoin-development@lists.sourceforge.net>;
Fri, 25 Apr 2014 13:48:52 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.224.125.74 with SMTP id x10mr14813205qar.99.1398458932569;
Fri, 25 Apr 2014 13:48:52 -0700 (PDT)
Received: by 10.140.25.86 with HTTP; Fri, 25 Apr 2014 13:48:52 -0700 (PDT)
In-Reply-To: <201404252026.56765.luke@dashjr.org>
References: <CAE-z3OXe4fG2S274qcgpGsXA=ZhhJQneEDqLYvNWZT8U9y_NLA@mail.gmail.com>
<201404251917.49826.luke@dashjr.org>
<CAE-z3OX5_POg9kFoz-LsGhuLRA6qFPcNXoECLhewe+o-+Pw2gA@mail.gmail.com>
<201404252026.56765.luke@dashjr.org>
Date: Fri, 25 Apr 2014 21:48:52 +0100
Message-ID: <CAE-z3OUKwpKcX27N1PKqXEHOKh+r6UD3FHioRt6TMMLVPoLjOw@mail.gmail.com>
From: Tier Nolan <tier.nolan@gmail.com>
To: Luke-Jr <luke@dashjr.org>
Content-Type: multipart/alternative; boundary=001a11c30886e8dcc204f7e417fe
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: 1Wdn3K-00069z-0b
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] BIP - Selector Script
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: Fri, 25 Apr 2014 20:48:59 -0000
--001a11c30886e8dcc204f7e417fe
Content-Type: text/plain; charset=UTF-8
On Fri, Apr 25, 2014 at 9:26 PM, Luke-Jr <luke@dashjr.org> wrote:
> They define standard for interoperability between
> software. So, if you want nodes to relay these transactions, you need to
> convince them, not merely write a BIP for the transaction format.
I agree with you in theory, each miner could decide their inclusion rules
for themselves.
In practice, if the reference client is updated, then most miners will
accept those transactions. In addition, it would eventually propagate to
alt-coins (or at least the supported ones).
I could simply submit the changes as a pull request for the reference
client, but I was hoping that by doing it this way, it would increase the
odds of it being accepted.
> Defining a BIP for cross-chain trading would be one way to do that.
>
I don't think it quite requires the same coordination in the short term. I
could write up the sequence as an info BIP.
The malleability "issue" has been known for years.
> I wouldn't expect any special effort made to fix it...
>
It is possible to tweak the protocol so that it still works. However, it
means that 3rd parties are required (that could go in the BIP too).
> There is some ongoing discussion of a softfork to basically redo the Script
> language entirely, but it will take quite a bit of time and development
> before
> we'll see it in the wild.
>
Implementing multi-P2SH gets a lot of the benefits of MAST, in terms of
efficiency.
>
> Luke
>
> P.S. Did the BIP editor assign these numbers? If not, best to keep them
> numberless until assigned, to avoid confusion when people Google the real
> BIP
> 44 and 45...
>
Not yet, but that is just my personal repo. I did email gmaxwell, but he
said that they can't be assigned until some discussion has happened.
I take your point that the name appears in the link though, so could cause
issues with searching.
>
> ------------------------------------------------------------------------------
> Start Your Social Network Today - Download eXo Platform
> Build your Enterprise Intranet with eXo Platform Software
> Java Based Open Source Intranet - Social, Extensible, Cloud Ready
> Get Started Now And Turn Your Intranet Into A Collaboration Platform
> http://p.sf.net/sfu/ExoPlatform
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--001a11c30886e8dcc204f7e417fe
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">On Fri, Apr 25, 2014 at 9:26 PM, Luke-Jr <span dir=3D"ltr"=
><<a href=3D"mailto:luke@dashjr.org" target=3D"_blank">luke@dashjr.org</=
a>></span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gmail_quot=
e"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex">
They define standard for interoperability between<br>
software. So, if you want nodes to relay these transactions, you need to<br=
>
convince them, not merely write a BIP for the transaction format.</blockquo=
te><div><br></div><div>I agree with you in theory, each miner could decide =
their inclusion rules for themselves.<br><br>In practice, if the reference =
client is updated, then most miners will accept those transactions.=C2=A0 I=
n addition, it would eventually propagate to alt-coins (or at least the sup=
ported ones).<br>
<br></div><div>I could simply submit the changes as a pull request for the =
reference client, but I was hoping that by doing it this way, it would incr=
ease the odds of it being accepted.<br></div><div>=C2=A0</div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex">
Defining a BIP for cross-chain trading would be one way to do that.<br></b=
lockquote><div><br></div><div>I don't think it quite requires the same =
coordination in the short term.=C2=A0 I could write up the sequence as an i=
nfo BIP.<br>
</div><br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex">The malleability "issue"=
has been known for years.<br>
I wouldn't expect any special effort made to fix it...<br></blockquote>=
<div><br></div><div>It is possible to tweak the protocol so that it still w=
orks.=C2=A0 However, it means that 3rd parties are required (that could go =
in the BIP too).<br>
</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
There is some ongoing discussion of a softfork to basically redo the Script=
<br>
language entirely, but it will take quite a bit of time and development bef=
ore<br>
we'll see it in the wild.<br></blockquote><div><br></div><div>Implement=
ing multi-P2SH gets a lot of the benefits of MAST, in terms of efficiency.<=
br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Luke<br>
</font></span><br>
P.S. Did the BIP editor assign these numbers? If not, best to keep them<br>
numberless until assigned, to avoid confusion when people Google the real B=
IP<br>
44 and 45...<br></blockquote><div><br></div><div>Not yet, but that is just =
my personal repo.=C2=A0 I did email gmaxwell, but he said that they can'=
;t be assigned until some discussion has happened.<br></div><div>=C2=A0<br>=
</div>
<div>I take your point that the name appears in the link though, so could c=
ause issues with searching.<br></div><div><br></div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex">
<div class=3D"HOEnZb"><div class=3D"h5"><br>
---------------------------------------------------------------------------=
---<br>
Start Your Social Network Today - Download eXo Platform<br>
Build your Enterprise Intranet with eXo Platform Software<br>
Java Based Open Source Intranet - Social, Extensible, Cloud Ready<br>
Get Started Now And Turn Your Intranet Into A Collaboration Platform<br>
<a href=3D"http://p.sf.net/sfu/ExoPlatform" target=3D"_blank">http://p.sf.n=
et/sfu/ExoPlatform</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</div></div></blockquote></div><br></div></div>
--001a11c30886e8dcc204f7e417fe--
|
