From mboxrd@z Thu Jan 1 00:00:00 1970 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 ) 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 ; 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: From: Melvin Carvalho To: Adam Back 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 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 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



On 19 May 2013 15:23, Adam Back <adam@cypherspace.org> wrote:
Is there a way to experiment with new featur= es - 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?<= br>
eg lets say some form of merged mine where an alt-coin lets call it
bitcoin-staging? =A0where the coins are the same coins as on bitcoin, the 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=
move them to bitcoin-staging and vice versa (ie exchange them 1:1
cryptographically, no exchange).

Did anyone figure anything like that out? =A0Seems vaguely doable and
maybe productive. =A0The only people with coins at risk of defects in a new=
feature, or insufficiently well tested novel feature are people with coins<= br> on bitcoin-staging.

Yes I know about bitcoin-test this is not it. =A0I mean a real live system,=
with live value, but that is intentionally wanting to avoid forking bitcoin= s
parameters, nor value, nor mindshare dillution. =A0In this way something potentially interesting could move forward faster, and be les risky to the<= br> main bitcoin network. =A0eg 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 afte= r
extensive real-world validation with real-money at stake (by early
adopters).

Interesting idea.=A0 I wonde= r if ripple could be used to set up a transfer system between the 'main= ' and 'staging' systems ...
=A0

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.s= f.net/sfu/alienvault_d2d
_______________________________________________
Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment

--089e0160a6f4bba92304df2f8658--