From: Adam Back <adam@cypherspace•org>
To: Melvin Carvalho <melvincarvalho@gmail•com>
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?)
Date: Thu, 21 Nov 2013 22:11:57 +0100 [thread overview]
Message-ID: <20131121211157.GA4871@netbook.cypherspace.org> (raw)
In-Reply-To: <CAKaEYhJVLhRfcX7T62S8fx+cPKJepQCd4gBnqv5cUJzcGM7MHA@mail.gmail.com>
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 ...
next prev parent reply other threads:[~2013-11-21 21:25 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-19 13:23 [Bitcoin-development] is there a way to do bitcoin-staging? Adam Back
2013-05-19 15:08 ` Peter Vessenes
2013-05-20 6:34 ` Alan Reiner
2013-10-14 18:08 ` Adam Back
2013-10-14 18:21 ` Jeff Garzik
2013-11-21 20:22 ` coinscoins
2013-11-21 20:35 ` Melvin Carvalho
2013-11-21 21:11 ` Adam Back [this message]
2014-03-16 22:58 ` [Bitcoin-development] 2-way pegging (Re: is there a way to do bitcoin-staging?) Adam Back
2014-03-16 23:22 ` Jorge Timón
2014-03-17 15:55 ` Gregory Maxwell
2013-10-14 18:43 ` [Bitcoin-development] is there a way to do bitcoin-staging? Michael Gronager
2013-10-14 20:20 ` Alan Reiner
2013-05-22 3:37 ` zooko
2013-05-22 4:12 ` Jeff Garzik
2013-05-20 7:12 ` Luke-Jr
2013-06-13 13:39 ` Adam Back
2013-06-14 19:20 ` Peter Todd
2013-06-14 20:50 ` Adam Back
2013-06-14 21:10 ` Luke-Jr
2013-06-14 21:25 ` Andreas Petersson
2013-06-15 0:09 ` Dennison Bertram
2013-06-15 1:57 ` Luke-Jr
2013-06-15 8:43 ` Dennison Bertram
2013-06-15 11:18 ` Melvin Carvalho
2013-06-15 13:26 ` Dennison Bertram
2013-06-16 15:46 ` Dennison Bertram
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131121211157.GA4871@netbook.cypherspace.org \
--to=adam@cypherspace$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=melvincarvalho@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox