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-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1X7jPY-0003vA-I7 for bitcoin-development@lists.sourceforge.net; Thu, 17 Jul 2014 10:59:40 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.217.174 as permitted sender) client-ip=209.85.217.174; envelope-from=melvincarvalho@gmail.com; helo=mail-lb0-f174.google.com; Received: from mail-lb0-f174.google.com ([209.85.217.174]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1X7jPX-0007sC-Aa for bitcoin-development@lists.sourceforge.net; Thu, 17 Jul 2014 10:59:40 +0000 Received: by mail-lb0-f174.google.com with SMTP id c11so1593021lbj.33 for ; Thu, 17 Jul 2014 03:59:32 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.152.8.109 with SMTP id q13mr31376597laa.31.1405594772701; Thu, 17 Jul 2014 03:59:32 -0700 (PDT) Received: by 10.112.112.106 with HTTP; Thu, 17 Jul 2014 03:59:32 -0700 (PDT) Date: Thu, 17 Jul 2014 12:59:32 +0200 Message-ID: From: Melvin Carvalho To: Bitcoin Dev Content-Type: multipart/alternative; boundary=001a11c36472200b4f04fe6189e2 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: 1X7jPX-0007sC-Aa Subject: [Bitcoin-development] Mining Hashrate Caps 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: Thu, 17 Jul 2014 10:59:40 -0000 --001a11c36472200b4f04fe6189e2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I noticed this article today. GHash Commits to 40% Hashrate Cap at Bitcoin Mining Summit http://www.coindesk.com/ghash-commits-40-hashrate-cap-bitcoin-mining-summit= / Here's a quote from Satoshi when the mining arms race began: "We should have a gentleman=E2=80=99s agreement to postpone the GPU arms ra= ce as long as we can for the good of the network. It=E2=80=99s much easer to get = new users up to speed if they don=E2=80=99t have to worry about GPU drivers and compatibility. It=E2=80=99s nice how anyone with just a CPU can compete fai= rly equally right now." Maybe outdated now, but I thought it was interesting. --001a11c36472200b4f04fe6189e2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I noticed this article today.=C2= =A0

GHash Commits to 40% Hashrate Cap at Bitcoin Mining Summit
<= br>http://www.coindesk.com/ghash-commits-40-hashrate-cap-bitc= oin-mining-summit/

Here's a quote from Satoshi when the mining arms race b= egan:

"We should have a gentleman=E2=80=99s agreement to postpo= ne the GPU arms race as long as we can for the good of the network. It=E2= =80=99s much easer to get new users up to speed if they don=E2=80=99t have = to worry about GPU drivers and compatibility. It=E2=80=99s nice how anyone = with just a CPU can compete fairly equally right now."

Maybe outdated now, but I thought it was interesting.
=
--001a11c36472200b4f04fe6189e2-- From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1X7mJH-0007iO-R9 for bitcoin-development@lists.sourceforge.net; Thu, 17 Jul 2014 14:05:25 +0000 Received: from mail-qc0-f170.google.com ([209.85.216.170]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1X7mJF-0001XZ-U6 for bitcoin-development@lists.sourceforge.net; Thu, 17 Jul 2014 14:05:23 +0000 Received: by mail-qc0-f170.google.com with SMTP id c9so2155894qcz.29 for ; Thu, 17 Jul 2014 07:05:16 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:organization:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=dwSyLvRgyLZbHe9JpkG6bd3h7nr4n0LNcut8PBmTr8w=; b=aLLGY6z/D7lkyOXhrkdy1gZaxNi91yFF5It4SqtseOQNZsJ7W3AsVWDI1kJ8tWZn2O ao0txmE5M7SYXp78FhylOTf5YD1Vjhy9jx2d1/OOF3gnxj4cifgYODf6oCkIoLRpCz3E S7SNtDHiE4UwXnkL2ZGyVAP1dv1mCMwiJz9iSogWxfuenBdrph2ljPJBjh6oEbErldex ICty/Mw4dl+bmu0QgDcP6LSYn0hLOORRMjLzOA3BH4GLbR3DR1l3L4k5/fFdGc7OHVF+ e69w906ttq/Qi3IQU/x75T8jcBGaNgi8ePxixPKmdSV7Ts4N4hgI51YhPBqoo8Ouv++F ul/A== X-Gm-Message-State: ALoCoQlZL4kWQGWN1hPZlCyJPGmE1vrjtb7QM9ycsWprUXWHkcO86Xyv5B12oAchSpQhC4L3Yb5k X-Received: by 10.224.137.193 with SMTP id x1mr60098434qat.0.1405604122121; Thu, 17 Jul 2014 06:35:22 -0700 (PDT) Received: from [192.168.127.231] ([207.253.217.242]) by mx.google.com with ESMTPSA id j9sm4512475qao.46.2014.07.17.06.35.21 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 17 Jul 2014 06:35:21 -0700 (PDT) Message-ID: <53C7D118.4050908@monetize.io> Date: Thu, 17 Jul 2014 09:35:20 -0400 From: Mark Friedenbach Organization: Monetize.io Inc. User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. X-Headers-End: 1X7mJF-0001XZ-U6 Subject: Re: [Bitcoin-development] Mining Hashrate Caps 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: Thu, 17 Jul 2014 14:05:28 -0000 Can someone explain to these guys and the public why promising to limit yourselves to *only* a 50% chance of successfully double-spending a 6 confirm transaction is still not acceptable? q=0.4 z=0 P=1 z=1 P=0.828861 z=2 P=0.736403 z=3 P=0.664168 z=4 P=0.603401 z=5 P=0.550625 z=6 P=0.50398 z=7 P=0.462301 z=8 P=0.424782 z=9 P=0.390828 z=10 P=0.359976 z=11 P=0.331858 z=12 P=0.306167 z=13 P=0.282649 z=14 P=0.261083 z=15 P=0.24128 z=16 P=0.223076 z=17 P=0.206324 z=18 P=0.190896 z=19 P=0.176676 On 07/17/2014 06:59 AM, Melvin Carvalho wrote: > I noticed this article today. > > GHash Commits to 40% Hashrate Cap at Bitcoin Mining Summit > > http://www.coindesk.com/ghash-commits-40-hashrate-cap-bitcoin-mining-summit/ > > Here's a quote from Satoshi when the mining arms race began: > > "We should have a gentleman’s agreement to postpone the GPU arms race as > long as we can for the good of the network. It’s much easer to get new > users up to speed if they don’t have to worry about GPU drivers and > compatibility. It’s nice how anyone with just a CPU can compete fairly > equally right now." > > Maybe outdated now, but I thought it was interesting. > > > ------------------------------------------------------------------------------ > Want fast and easy access to all the code in your enterprise? Index and > search up to 200,000 lines of code with a free copy of Black Duck > Code Sight - the same software that powers the world's largest code > search on Ohloh, the Black Duck Open Hub! Try it now. > http://p.sf.net/sfu/bds > > > > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1X7oQx-00076f-RZ for bitcoin-development@lists.sourceforge.net; Thu, 17 Jul 2014 16:21:27 +0000 X-ACL-Warn: Received: from mail.dtrt.org ([207.192.75.234]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1X7oQw-0005zb-FQ for bitcoin-development@lists.sourceforge.net; Thu, 17 Jul 2014 16:21:27 +0000 Received: from harding by mail.dtrt.org with local (Exim 4.72) (envelope-from ) id 1X7nt9-0005v2-LN; Thu, 17 Jul 2014 11:46:31 -0400 Date: Thu, 17 Jul 2014 11:45:06 -0400 From: "David A. Harding" To: Mark Friedenbach Message-ID: <20140717154506.GA19666@localhost.localdomain> References: <53C7D118.4050908@monetize.io> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <53C7D118.4050908@monetize.io> User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Score: -0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.0 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1X7oQw-0005zb-FQ Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] Mining Hashrate Caps 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: Thu, 17 Jul 2014 16:21:28 -0000 On Thu, Jul 17, 2014 at 09:35:20AM -0400, Mark Friedenbach wrote: > Can someone explain to these guys and the public why promising to limit > yourselves to *only* a 50% chance of successfully double-spending a 6 > confirm transaction is still not acceptable? Hi, Mark. We were asked on the bitcoin-documentation mailing list about a month ago to work on something like this and we're getting close to a pull request for the Bitcoin.org website. There's a preview here: http://dg0.dtrt.org/en/mining#lucky-attack (Remember, it's a preview and still being actively written/edited.) Discussion about that doc belongs on the bitcoin-documentation mailing list. Here's the particular thread: https://groups.google.com/forum/#!topic/bitcoin-documentation/PKwBcroWGGg Thanks, -Dave -- David A. Harding