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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <melvincarvalho@gmail.com>) id 1UnoVP-00069G-Mv
for bitcoin-development@lists.sourceforge.net;
Sat, 15 Jun 2013 11:18:51 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.215.51 as permitted sender)
client-ip=209.85.215.51; envelope-from=melvincarvalho@gmail.com;
helo=mail-la0-f51.google.com;
Received: from mail-la0-f51.google.com ([209.85.215.51])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1UnoVO-0005Qa-Ei
for bitcoin-development@lists.sourceforge.net;
Sat, 15 Jun 2013 11:18:51 +0000
Received: by mail-la0-f51.google.com with SMTP id fq12so1209516lab.24
for <bitcoin-development@lists.sourceforge.net>;
Sat, 15 Jun 2013 04:18:43 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.152.26.166 with SMTP id m6mr3002777lag.50.1371295123742;
Sat, 15 Jun 2013 04:18:43 -0700 (PDT)
Received: by 10.112.2.8 with HTTP; Sat, 15 Jun 2013 04:18:43 -0700 (PDT)
In-Reply-To: <20130519132359.GA12366@netbook.cypherspace.org>
References: <20130519132359.GA12366@netbook.cypherspace.org>
Date: Sat, 15 Jun 2013 13:18:43 +0200
Message-ID: <CAKaEYhJfrszqC=7L9inkSH5+9nzUzRLx6Oq+C6bA+fDXXLfh8Q@mail.gmail.com>
From: Melvin Carvalho <melvincarvalho@gmail.com>
To: Adam Back <adam@cypherspace.org>
Content-Type: multipart/alternative; boundary=089e0160a6f4bba92304df2f8658
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
(melvincarvalho[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: 1UnoVO-0005Qa-Ei
Cc: Bitcoin-Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] is there a way to do bitcoin-staging?
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, 15 Jun 2013 11:18:51 -0000
--089e0160a6f4bba92304df2f8658
Content-Type: text/plain; charset=ISO-8859-1
On 19 May 2013 15:23, Adam Back <adam@cypherspace.org> wrote:
> Is there a way to experiment with new features - eg committed coins - that
> doesnt involve an altcoin in the conventional sense, and also doesnt impose
> a big testing burden on bitcoin main which is a security and testing risk?
>
> eg lets say some form of merged mine where an alt-coin lets call it
> bitcoin-staging? where the coins are the same coins as on bitcoin, the
> mining power goes to bitcoin main, so some aspect of merged mining, but no
> native mining. and ability to use bitcoins by locking them on bitcoin to
> move them to bitcoin-staging and vice versa (ie exchange them 1:1
> cryptographically, no exchange).
>
> Did anyone figure anything like that out? Seems vaguely doable and
> maybe productive. The only people with coins at risk of defects in a new
> feature, or insufficiently well tested novel feature are people with coins
> on bitcoin-staging.
>
> Yes I know about bitcoin-test this is not it. I mean a real live system,
> with live value, but that is intentionally wanting to avoid forking
> bitcoins
> parameters, nor value, nor mindshare dillution. In this way something
> potentially interesting could move forward faster, and be les risky to the
> main bitcoin network. eg particularly defenses against
>
> It might also be a more real world test test (after bitcoin-test) because
> some parameters are different on test, and some issues may not manifest
> without more real activity.
>
> Then also bitcoin could cherry pick interesting patches and merge them
> after
> extensive real-world validation with real-money at stake (by early
> adopters).
>
Interesting idea. I wonder if ripple could be used to set up a transfer
system between the 'main' and 'staging' systems ...
>
> Adam
>
>
> ------------------------------------------------------------------------------
> AlienVault Unified Security Management (USM) platform delivers complete
> security visibility with the essential security capabilities. Easily and
> efficiently configure, manage, and operate all of your security controls
> from a single console and one unified framework. Download a free trial.
> http://p.sf.net/sfu/alienvault_d2d
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--089e0160a6f4bba92304df2f8658
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On 19 May 2013 15:23, Adam Back <span dir=3D"ltr"><<a href=3D"ma=
ilto:adam@cypherspace.org" target=3D"_blank">adam@cypherspace.org</a>></=
span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Is there a way to experiment with new featur=
es - eg committed coins - that<br>
doesnt involve an altcoin in the conventional sense, and also doesnt impose=
<br>
a big testing burden on bitcoin main which is a security and testing risk?<=
br>
<br>
eg lets say some form of merged mine where an alt-coin lets call it<br>
bitcoin-staging? =A0where the coins are the same coins as on bitcoin, the<b=
r>
mining power goes to bitcoin main, so some aspect of merged mining, but no<=
br>
native mining. =A0and ability to use bitcoins by locking them on bitcoin to=
<br>
move them to bitcoin-staging and vice versa (ie exchange them 1:1<br>
cryptographically, no exchange).<br>
<br>
Did anyone figure anything like that out? =A0Seems vaguely doable and<br>
maybe productive. =A0The only people with coins at risk of defects in a new=
<br>
feature, or insufficiently well tested novel feature are people with coins<=
br>
on bitcoin-staging.<br>
<br>
Yes I know about bitcoin-test this is not it. =A0I mean a real live system,=
<br>
with live value, but that is intentionally wanting to avoid forking bitcoin=
s<br>
parameters, nor value, nor mindshare dillution. =A0In this way something<br=
>
potentially interesting could move forward faster, and be les risky to the<=
br>
main bitcoin network. =A0eg particularly defenses against<br>
<br>
It might also be a more real world test test (after bitcoin-test) because<b=
r>
some parameters are different on test, and some issues may not manifest<br>
without more real activity.<br>
<br>
Then also bitcoin could cherry pick interesting patches and merge them afte=
r<br>
extensive real-world validation with real-money at stake (by early<br>
adopters).<br></blockquote><div><br></div><div>Interesting idea.=A0 I wonde=
r if ripple could be used to set up a transfer system between the 'main=
' and 'staging' systems ...<br></div><div>=A0</div><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid=
;padding-left:1ex">
<br>
Adam<br>
<br>
---------------------------------------------------------------------------=
---<br>
AlienVault Unified Security Management (USM) platform delivers complete<br>
security visibility with the essential security capabilities. Easily and<br=
>
efficiently configure, manage, and operate all of your security controls<br=
>
from a single console and one unified framework. Download a free trial.<br>
<a href=3D"http://p.sf.net/sfu/alienvault_d2d" target=3D"_blank">http://p.s=
f.net/sfu/alienvault_d2d</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>
</blockquote></div><br></div></div>
--089e0160a6f4bba92304df2f8658--
|
