diff options
| author | Melvin Carvalho <melvincarvalho@gmail.com> | 2013-06-15 13:18:43 +0200 |
|---|---|---|
| committer | bitcoindev <bitcoindev@gnusha.org> | 2013-06-15 11:18:51 +0000 |
| commit | d155161874bc3319fae7c56ea610b5db3fe81672 (patch) | |
| tree | f92a3895cddd19193da25dec59d380b60010d4f4 | |
| parent | 9fa003edc8cb5b189b2cfa7155cde1a3678105af (diff) | |
| download | pi-bitcoindev-d155161874bc3319fae7c56ea610b5db3fe81672.tar.gz pi-bitcoindev-d155161874bc3319fae7c56ea610b5db3fe81672.zip | |
Re: [Bitcoin-development] is there a way to do bitcoin-staging?
| -rw-r--r-- | a5/a98ea003e9480f44ff242e277ca732d901f72f | 199 |
1 files changed, 199 insertions, 0 deletions
diff --git a/a5/a98ea003e9480f44ff242e277ca732d901f72f b/a5/a98ea003e9480f44ff242e277ca732d901f72f new file mode 100644 index 000000000..baa9c65e0 --- /dev/null +++ b/a5/a98ea003e9480f44ff242e277ca732d901f72f @@ -0,0 +1,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-- + + |