From: Pieter Wuille <pieter.wuille@gmail•com>
To: thomasV1@gmx•de
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] BIP22/getmemorypool
Date: Tue, 12 Jun 2012 12:50:40 +0200 [thread overview]
Message-ID: <20120612105038.GA29784@vps7135.xlshosting.net> (raw)
In-Reply-To: <20120611181022.10710@gmx.net>
On Mon, Jun 11, 2012 at 08:10:22PM +0200, thomasV1@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 pool customers" features and what are the "will be used by
> > less than 5% of pool customers" features.
>
> will be used by Electrum servers
Please. This is not about whether getmemorypool is useful (at least I am
a big fan of BIP22's big picture). It's about whether it needs 20 optional
features.
--
Pieter
prev parent reply other threads:[~2012-06-12 10:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-10 9:03 Pieter Wuille
2012-06-10 14:18 ` Pieter Wuille
2012-06-11 17:47 ` Gavin Andresen
2012-06-11 18:10 ` thomasV1
2012-06-12 10:50 ` Pieter Wuille [this message]
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=20120612105038.GA29784@vps7135.xlshosting.net \
--to=pieter.wuille@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=thomasV1@gmx$(echo .)de \
/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