On Mon, Jun 11, 2012 at 08:10:22PM +0200, thoma...@gmx.de wrote:
>
> > discussion back here. The executive summary: Pieter and I feel like
> > BIP 22 is overly complicated, and would like it to be simpler. I'd
> > especially like to hear what people think will be the "will be used by
> > lots of
> discussion back here. The executive summary: Pieter and I feel like
> BIP 22 is overly complicated, and would like it to be simpler. I'd
> especially like to hear what people think will be the "will be used by
> lots of pool customers" features and what are the "will be used by
> less than 5%
I think the sourceforge mailing list system had the hiccups this
weekend; sorry for Pieter's messages appearing in your inbox multiple
times, it is not his fault.
I deleted the extra copies from the mailing list archives.
As for the contents of his message, since this mailing list was not
workin
Hello everyone,
Luke's getmemorypool/BIP22 pull request has been open for a long time, and
didn't receive too much discussion.
I think that having a stable and flexible API for negotiating block
generation is important to be standardized. The fact that it allows moving
block generation to special
- Forwarded message from Pieter Wuille -
Date: Sun, 10 Jun 2012 01:10:54 +0200
From: Pieter Wuille
To: bitcoin-development@lists.sourceforge.net
Subject: getmemorypool
User-Agent: Mutt/1.5.20 (2009-06-14)
Hello everyone,
Luke's getmemorypool/BIP22 pull request has been open for a long
5 matches
Mail list logo
