From mboxrd@z Thu Jan 1 00:00:00 1970 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 ) id 1UO3TP-0000Bk-Jx for bitcoin-development@lists.sourceforge.net; Fri, 05 Apr 2013 10:02:19 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.215.53 as permitted sender) client-ip=209.85.215.53; envelope-from=gmaxwell@gmail.com; helo=mail-la0-f53.google.com; Received: from mail-la0-f53.google.com ([209.85.215.53]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1UO3TO-0004sa-MH for bitcoin-development@lists.sourceforge.net; Fri, 05 Apr 2013 10:02:19 +0000 Received: by mail-la0-f53.google.com with SMTP id fp12so435469lab.40 for ; Fri, 05 Apr 2013 03:02:12 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.112.161.97 with SMTP id xr1mr2705434lbb.15.1365156131908; Fri, 05 Apr 2013 03:02:11 -0700 (PDT) Received: by 10.112.134.164 with HTTP; Fri, 5 Apr 2013 03:02:11 -0700 (PDT) In-Reply-To: References: Date: Fri, 5 Apr 2013 03:02:11 -0700 Message-ID: From: Gregory Maxwell To: Mike Hearn Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -1.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 (gmaxwell[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -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: 1UO3TO-0004sa-MH Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] A mining pool at 46% 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: Fri, 05 Apr 2013 10:02:19 -0000 On Fri, Apr 5, 2013 at 2:48 AM, Mike Hearn wrote: > but I think p2pool still has a lot of problems dealing with > FPGA/ASIC hardware and it hasn't been growing for a long time. As an aside and a clarification=E2=80=94 P2pool works great with FPGAs, and one of the largest FPGA farms I've heard of uses it. But it doesn't work well the old BFL FPGA miners=E2=80=94 because they have insane latency= . Likewise it doesn't currently work well with Avalon, again because of insane latency. P2pool uses a 10 second sharechain in order to give miners low variance but that means that if you have a several second miner you'll end up subsidizing all the faster p2pool users somewhat. It was basically stable with the network until ASICminer came online mining on BTCguild mostly and the first avalons started to ship, and then the network went up 10TH in a couple weeks (and now 15TH) while P2Pool stayed mostly constant. ForrestV (the author and maintainer of the P2pool software) would love to work on making Avalon and other higher latency devices first class supported on P2Pool, but he doesn't have one=E2=80=94 and frankly, all the people who have them aren't super eager to fuss around with a 5BTC/day revenue stream, especially since the avalon firmware (and its internal copy of cgminer) itself has a bunch of quirks and bugs that are still getting worked out... and I do believe that p2pool helps reduce concerns around mining pool centralization. ... but I think as a community we don't always do a great job at supporting people who work on infrastructure=E2=80=94 even just making sure to get them what they need= to keep giving us free stuff=E2=80=94, we just assume they're super rich Bitco= in old hands, but that often isn't true.