From: Jeff Garzik <jgarzik@exmulti.com>
To: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] Protocol changes for SPV clients: mempool, getdata commands
Date: Mon, 13 Aug 2012 11:57:59 -0400 [thread overview]
Message-ID: <CA+8xBpevWfyvb7d6dBhMB4s=p4w8GdO7s+WDUo6zoJYGg3+b9A@mail.gmail.com> (raw)
A small change to the protocol is proposed for satoshi client v0.7
(upcoming release):
Add 'mempool' P2P command, and extend 'getdata' behavior
https://github.com/bitcoin/bitcoin/pull/1641
The genesis of this command is to permit SPV clients to access the
memory pool, but secondary uses include diagnostics and miner download
(so that miners won't miss lucrative TX's due to node restart).
"getdata" behavior is extended to include any memory pool transaction,
relaxing a previous "getdata" restriction.
Didn't feel this warranted a BIP, but can write one if people really want one.
--
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti.com
next reply other threads:[~2012-08-13 15:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-13 15:57 Jeff Garzik [this message]
2012-08-14 4:55 ` [Bitcoin-development] Protocol changes for SPV clients: mempool, getdata commands Wladimir
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='CA+8xBpevWfyvb7d6dBhMB4s=p4w8GdO7s+WDUo6zoJYGg3+b9A@mail.gmail.com' \
--to=jgarzik@exmulti.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