diff options
| author | Gregory Maxwell <gmaxwell@gmail.com> | 2014-07-17 16:34:21 -0700 |
|---|---|---|
| committer | bitcoindev <bitcoindev@gnusha.org> | 2014-07-17 23:34:29 +0000 |
| commit | 667e785875174a40c035baba614af9692de86bae (patch) | |
| tree | 6146e6e82ecf759a828dc94e813fdb5fff0ed90b | |
| parent | 069892fb7565beaf2df7eba8b7d5aae48219a05b (diff) | |
| download | pi-bitcoindev-667e785875174a40c035baba614af9692de86bae.tar.gz pi-bitcoindev-667e785875174a40c035baba614af9692de86bae.zip | |
Re: [Bitcoin-development] Squashing redundant tx data in blocks on the wire
| -rw-r--r-- | 1a/b9b07199cd6566e04f79a5f3477f7dfeed5a8e | 79 |
1 files changed, 79 insertions, 0 deletions
diff --git a/1a/b9b07199cd6566e04f79a5f3477f7dfeed5a8e b/1a/b9b07199cd6566e04f79a5f3477f7dfeed5a8e new file mode 100644 index 000000000..3b46a0fc9 --- /dev/null +++ b/1a/b9b07199cd6566e04f79a5f3477f7dfeed5a8e @@ -0,0 +1,79 @@ +Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] + helo=mx.sourceforge.net) + by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) + (envelope-from <gmaxwell@gmail.com>) id 1X7vC1-0004vQ-Tl + for bitcoin-development@lists.sourceforge.net; + Thu, 17 Jul 2014 23:34:29 +0000 +Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com + designates 209.85.215.43 as permitted sender) + client-ip=209.85.215.43; envelope-from=gmaxwell@gmail.com; + helo=mail-la0-f43.google.com; +Received: from mail-la0-f43.google.com ([209.85.215.43]) + by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) + (Exim 4.76) id 1X7vC0-0002t6-Eh + for bitcoin-development@lists.sourceforge.net; + Thu, 17 Jul 2014 23:34:29 +0000 +Received: by mail-la0-f43.google.com with SMTP id hr17so2319595lab.16 + for <bitcoin-development@lists.sourceforge.net>; + Thu, 17 Jul 2014 16:34:21 -0700 (PDT) +MIME-Version: 1.0 +X-Received: by 10.112.16.230 with SMTP id j6mr471801lbd.90.1405640061886; Thu, + 17 Jul 2014 16:34:21 -0700 (PDT) +Received: by 10.112.35.138 with HTTP; Thu, 17 Jul 2014 16:34:21 -0700 (PDT) +In-Reply-To: <CA+iPb=EaX=bvOjNtZ+LnYTMRLQQ9nFcrefAkBdv8eActoX_b8A@mail.gmail.com> +References: <CA+iPb=EaX=bvOjNtZ+LnYTMRLQQ9nFcrefAkBdv8eActoX_b8A@mail.gmail.com> +Date: Thu, 17 Jul 2014 16:34:21 -0700 +Message-ID: <CAAS2fgSz0xS_OJKx-Xvw9GWkeJXEOL5aFQ+2mC=y5RwKNRykRQ@mail.gmail.com> +From: Gregory Maxwell <gmaxwell@gmail.com> +To: Kaz Wesley <keziahw@gmail.com> +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: quoted-printable +X-Spam-Score: -1.6 (-) +X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. + See http://spamassassin.org/tag/ for more details. + -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for + sender-domain + 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider + (gmaxwell[at]gmail.com) + -0.0 SPF_PASS SPF: sender matches SPF record + -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from + author's domain + 0.1 DKIM_SIGNED Message has a DKIM or DK signature, + not necessarily valid + -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature +X-Headers-End: 1X7vC0-0002t6-Eh +Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net> +Subject: Re: [Bitcoin-development] Squashing redundant tx data in blocks on + the wire +X-BeenThere: bitcoin-development@lists.sourceforge.net +X-Mailman-Version: 2.1.9 +Precedence: list +List-Id: <bitcoin-development.lists.sourceforge.net> +List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, + <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> +List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> +List-Post: <mailto:bitcoin-development@lists.sourceforge.net> +List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> +List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, + <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> +X-List-Received-Date: Thu, 17 Jul 2014 23:34:30 -0000 + +On Thu, Jul 17, 2014 at 2:35 PM, Kaz Wesley <keziahw@gmail.com> wrote: +> A node should be able to forget invs it has seen without invalidating wha= +t +> peers +> know about its known txes. To allow for this, a node assembles a bloom +> filter of + +Another option would be to just guarantee to keep at least the last N +sent in each direction to bound memory usage. N could be negotiated. + +Going more complex than that may not have wins enough to justify it... +would be good to measure it. + + +(If you're not aware of it, check out=E2=80=94 +https://en.bitcoin.it/wiki/User:Gmaxwell/block_network_coding for a +more complex idea) + + |