From: Gregory Maxwell <gmaxwell@gmail•com>
To: Mike Hearn <mike@plan99•net>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] A mining pool at 46%
Date: Fri, 5 Apr 2013 03:02:11 -0700 [thread overview]
Message-ID: <CAAS2fgSvipRgVRSwBjLuhvbhJZvLtJW8XafzythmkApfzoc+3Q@mail.gmail.com> (raw)
In-Reply-To: <CANEZrP3S7b+uh2LW4vH=53opopLJRmmJ-_Uad6yEQxZ3kHW47A@mail.gmail.com>
On Fri, Apr 5, 2013 at 2:48 AM, Mike Hearn <mike@plan99•net> 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— 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— 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— 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— even just making sure to get them what they need to
keep giving us free stuff—, we just assume they're super rich Bitcoin
old hands, but that often isn't true.
next prev parent reply other threads:[~2013-04-05 10:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 9:30 Melvin Carvalho
2013-04-05 9:48 ` Mike Hearn
2013-04-05 10:02 ` Gregory Maxwell [this message]
2013-04-05 10:13 ` Melvin Carvalho
2013-04-05 12:12 ` Peter Todd
2013-04-08 12:32 ` Daryl Tucker
2013-04-05 10:50 ` Robert McKay
2013-04-05 9:52 ` Gregory Maxwell
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=CAAS2fgSvipRgVRSwBjLuhvbhJZvLtJW8XafzythmkApfzoc+3Q@mail.gmail.com \
--to=gmaxwell@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mike@plan99$(echo .)net \
/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