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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mark@monetize.io>) id 1We5xr-0000b0-2S
for bitcoin-development@lists.sourceforge.net;
Sat, 26 Apr 2014 17:00:35 +0000
Received: from mail-pa0-f49.google.com ([209.85.220.49])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1We5xn-0007vX-OK
for bitcoin-development@lists.sourceforge.net;
Sat, 26 Apr 2014 17:00:35 +0000
Received: by mail-pa0-f49.google.com with SMTP id lj1so4189347pab.8
for <bitcoin-development@lists.sourceforge.net>;
Sat, 26 Apr 2014 10:00:25 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:message-id:date:from:organization:user-agent
:mime-version:to:subject:references:in-reply-to:content-type
:content-transfer-encoding;
bh=wTHHWG/e2KaFB6/Z4C9i6Blerzm+5/AIy53TqzDOtF8=;
b=JOmKrnoYyrM10grGcKET4RY8/VItzDovrAmfkBFp9QVCjzTB8CvnHMvNaIevjsbDSS
U/J4ePH6iCv2p3fjRP0AbvODdPaSVfAkKoi+um7G9v+HFYtooUnuUsGM2sqa4BT3DXFh
0+eEbeWAInQHTNdc/UjcxPOm6Rj1RzxzkelgLgIWiFMBioPIi0/6ms8j2rrrIVPy3u8G
oHGed7SNIyEDiw2y5Gr2vO8aqMS1mQreIr5H6Q0jJ7ahkS1m5nE7K/yAEaqYqAQChQGp
L6ltrXYlYCtD2kzETjh7I2+q477IrbtXTvFZJc53jV7kBMctjHzwF9KE4W15XAo5DlVA
W3xQ==
X-Gm-Message-State: ALoCoQm/5EOaE1Cpe8RwcfGkTlpqeewufOHtntHat8t9mlelrO3Qudmmxdq7nIsQu36sgJc5O3Oh
X-Received: by 10.68.197.99 with SMTP id it3mr14923264pbc.37.1398531625663;
Sat, 26 Apr 2014 10:00:25 -0700 (PDT)
Received: from [192.168.127.239] (50-0-36-93.dsl.dynamic.sonic.net.
[50.0.36.93]) by mx.google.com with ESMTPSA id
id10sm23685684pbc.35.2014.04.26.10.00.23
for <bitcoin-development@lists.sourceforge.net>
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Sat, 26 Apr 2014 10:00:24 -0700 (PDT)
Message-ID: <535BE626.5050109@monetize.io>
Date: Sat, 26 Apr 2014 10:00:23 -0700
From: Mark Friedenbach <mark@monetize.io>
Organization: Monetize.io Inc.
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
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>
<CAE-z3OUKwpKcX27N1PKqXEHOKh+r6UD3FHioRt6TMMLVPoLjOw@mail.gmail.com>
In-Reply-To: <CAE-z3OUKwpKcX27N1PKqXEHOKh+r6UD3FHioRt6TMMLVPoLjOw@mail.gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1We5xn-0007vX-OK
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: Sat, 26 Apr 2014 17:00:35 -0000
I think you're misunderstanding the point. The way you get IsStandard
changed is that you make an application-oriented BIP detailing the use
of some new standard transaction type (say, generalized hash-locked
transactions for atomic swaps). We then discuss that proposal for its
technical merits and reach consensus about the best way to do, for
example, cross-chain atomic swaps. It is then implemented.
So please, focus on some BIP(s) detailing applications of hash-locked
transactions, and we will engage more constructively -- I promise that I
will as cross-chain atomic swaps scratch my itch as well.
On 04/25/2014 01:48 PM, Tier Nolan wrote:
> On Fri, Apr 25, 2014 at 9:26 PM, Luke-Jr <luke@dashjr.org
> <mailto: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
> <mailto:Bitcoin-development@lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
>
>
> ------------------------------------------------------------------------------
> 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
>
|
