From: Amir Taaki <zgenjix@yahoo.com>
To: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] BIP 22 - getmemorypool
Date: Mon, 30 Jul 2012 13:26:12 -0700 (PDT) [thread overview]
Message-ID: <1343679972.9880.YahooMailNeo@web121004.mail.ne1.yahoo.com> (raw)
Hi,
luke-jr wants me to split this BIP into 3 separate BIPs because he says that other devs felt it was too unfocused and covered too many topics. However this discussion took place on IRC, and I never saw any of it to ascertain what happened (BIP 1 says drafts should be evaluated on the mailing list).
I think a discussion of BIP 22 perhaps did happen on the mailing list, but I don't remember it. Sorry if that's the case.
Anyway before granting the permission to allow this proposal to be pared down, and new BIPs granted for the non-core parts of this proposal, I want to know what people think. I'm not a miner myself, so I'm prescient of my lack of knowledge in the topic.
https://en.bitcoin.it/wiki/BIP_0022
Thanks
next reply other threads:[~2012-07-30 20:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-30 20:26 Amir Taaki [this message]
2012-07-30 20:30 ` [Bitcoin-development] BIP 22 - getmemorypool Luke-Jr
2012-07-30 20:32 ` 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=1343679972.9880.YahooMailNeo@web121004.mail.ne1.yahoo.com \
--to=zgenjix@yahoo.com \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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