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-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 <adam@cypherspace.org>) id 1VjbkN-0005AZ-MV
for bitcoin-development@lists.sourceforge.net;
Thu, 21 Nov 2013 21:25:11 +0000
X-ACL-Warn:
Received: from mout.perfora.net ([74.208.4.194])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VjbkL-0000nN-ND
for bitcoin-development@lists.sourceforge.net;
Thu, 21 Nov 2013 21:25:11 +0000
Received: from netbook (c83-90.i07-21.onvol.net [92.251.83.90])
by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis)
id 0LlDCg-1V8t9B0PXa-00aOZ8; Thu, 21 Nov 2013 16:12:08 -0500
Received: by netbook (Postfix, from userid 1000)
id 714192E28B7; Thu, 21 Nov 2013 22:12:00 +0100 (CET)
Received: by flare (hashcash-sendmail, from uid 1000);
Thu, 21 Nov 2013 22:11:57 +0100
Date: Thu, 21 Nov 2013 22:11:57 +0100
From: Adam Back <adam@cypherspace.org>
To: Melvin Carvalho <melvincarvalho@gmail.com>
Message-ID: <20131121211157.GA4871@netbook.cypherspace.org>
References: <20130519132359.GA12366@netbook.cypherspace.org>
<CAMGNxUsGRyYWepSn4on+V9CJAj0J8oSXndo36OrrCyMhvKnoxA@mail.gmail.com>
<5199C3DE.901@gmail.com>
<20131014180807.GA32082@netbook.cypherspace.org>
<CAKaEYhJVLhRfcX7T62S8fx+cPKJepQCd4gBnqv5cUJzcGM7MHA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
In-Reply-To: <CAKaEYhJVLhRfcX7T62S8fx+cPKJepQCd4gBnqv5cUJzcGM7MHA@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Hashcash: 1:20:131121:melvincarvalho@gmail.com::nKl2vh9dD4ShIJZy:0000000000000
0000000000000000000000008cG8
X-Hashcash: 1:20:131121:etotheipi@gmail.com::rYtTGsSzTuaIM5D/:000000000000000000
00000000000000000000000053/S
X-Hashcash: 1:20:131121:bitcoin-development@lists.sourceforge.net::kXnRb4BMnlAK8
e+v:000000000000000000005A3l
X-Hashcash: 1:20:131121:adam@cypherspace.org::8JuuxRV5KxYKgvrg:00000000000000000
0000000000000000000000001OVF
X-Provags-ID: V02:K0:utiBq78VJH0aWA0SuCp5Moutoz29+Hc8yhJ6toRGkyW
QfSFntUttB3HWUH9e9jnKROlbOfOWSW1ODCCjDFFvybgD9gbcn
5vnsph0tOYnLDZQz3SllHVeYKDve1ZaZRMlQd0fGMg6xjBV2f4
TbPSd47+oHQziTmzM2J+dBUnSHTKnpb0VcxwYcJT84a73YtKJk
mqpRMm5h/LIWtWj5wcgncV5j28h7VST1r+8/8yushojByH/hjf
5OK6IM3QDXJ6j0QMaz2HDAcIcg8GFltwYzt4kI3iUb8x4BD54D
bxYa3Jr87/JmqnViG19yaXmx+7xGS60y2lC6C6MZ1zPebLKwjU
L/KWPMZyDw0qZJASYuGjhN8L9ISRIsjdaR3duJZwy
X-Spam-Score: 1.2 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
no trust [74.208.4.194 listed in list.dnswl.org]
1.2 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net
[Blocked - see <http://www.spamcop.net/bl.shtml?74.208.4.194>]
-0.0 SPF_HELO_PASS SPF: HELO matches SPF record
X-Headers-End: 1VjbkL-0000nN-ND
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] bitcoin 1.x & 0.x in parallel (Re: 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: Thu, 21 Nov 2013 21:25:11 -0000
Yeah but that sounds pretty much like test-net and starts a new digital
scarcity on an alpha-qa level network, with an implied promise that maybe if
you're lucky your coins might survive the alpha testing and have some value.
I'm not talking about some slightly stabler version of test-net.
Probably bitcoin staging is the wrong name. I mean like development of
bitcoin 1.x in parallel with bitcoin 0.x which includes like test net for
both, and strong (though maybe not quite as high) assurance of qa and care
as bitcoin 0.x. Just as a way to get features like Mark Freidenbach's
freimarket script extensions, and some of the disabled scripts validated on
1.x testnet and then after rigorous testing deployed onto 1.x Because they
are new features even with good testing that introduces non-zero risk, hence
the 1 way peg idea. Welcome to suggest better names for the idea...
Of course maybe the other issue is insufficient people with the skills and
motivation to support two parallel efforts.
It gives somewhere to code and test and then deploy clearly useful things
but that dont warrant a hard fork.
Adam
Melvin wrote:
> I think there may be a simpler way to do this.
> Create a new genesis block for a staging network, but in all other
> aspects, as far as possible, keep the properties the same as bitcoin.
> Do not actively be opposed to it being traded, but people need to know
> that, although there is no intention to reset the chain, new and
> potentially not fully tested, changes can be rolled into the network.
> Anyone mining staging coins should be prepared for the value to go to
> zero.
> Perhaps also a "straw poll" voting system could be set up for those
> that own staging coins could sign messages saying which patches they
> would like to test out next. When patches are stable in the staging
> area, they could be "promoted" to the main net ...
|
