From: Wladimir <laanwj@gmail•com>
To: Jeff Garzik <jgarzik@exmulti•com>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Protocol changes for SPV clients: mempool, getdata commands
Date: Tue, 14 Aug 2012 06:55:35 +0200 [thread overview]
Message-ID: <CA+s+GJD=1TOWB6JH9M2KeKv3vMNezPKGTh7RPYfmRbeFxcxstQ@mail.gmail.com> (raw)
In-Reply-To: <CA+8xBpevWfyvb7d6dBhMB4s=p4w8GdO7s+WDUo6zoJYGg3+b9A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 437 bytes --]
On Mon, Aug 13, 2012 at 5:57 PM, Jeff Garzik <jgarzik@exmulti•com> wrote:
> 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
Fully agree with the changes, but I think there should be a small BIP, for
consistency, and to make it documented for other client developers.
Wladimir
[-- Attachment #2: Type: text/html, Size: 852 bytes --]
prev parent reply other threads:[~2012-08-14 4:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-13 15:57 Jeff Garzik
2012-08-14 4:55 ` Wladimir [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='CA+s+GJD=1TOWB6JH9M2KeKv3vMNezPKGTh7RPYfmRbeFxcxstQ@mail.gmail.com' \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jgarzik@exmulti$(echo .)com \
/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