Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WcHFs-0005BZ-AW for bitcoin-development@lists.sourceforge.net; Mon, 21 Apr 2014 16:39:40 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.219.51 as permitted sender) client-ip=209.85.219.51; envelope-from=mh.in.england@gmail.com; helo=mail-oa0-f51.google.com; Received: from mail-oa0-f51.google.com ([209.85.219.51]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WcHFo-0002jy-UN for bitcoin-development@lists.sourceforge.net; Mon, 21 Apr 2014 16:39:40 +0000 Received: by mail-oa0-f51.google.com with SMTP id i4so4385080oah.24 for ; Mon, 21 Apr 2014 09:39:31 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.182.219.167 with SMTP id pp7mr577566obc.85.1398098371559; Mon, 21 Apr 2014 09:39:31 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.76.96.180 with HTTP; Mon, 21 Apr 2014 09:39:31 -0700 (PDT) In-Reply-To: <53554979.9020206@monetize.io> References: <52CDA01B-13BF-4BB8-AC9A-5FBBB324FD15@sant.ox.ac.uk> <53554089.1010503@monetize.io> <53554979.9020206@monetize.io> Date: Mon, 21 Apr 2014 18:39:31 +0200 X-Google-Sender-Auth: wbWsMouekcg0UmI5wgb6irP4IMI Message-ID: From: Mike Hearn To: Mark Friedenbach Content-Type: multipart/alternative; boundary=089e0141ab82cc46ef04f79024e2 X-Spam-Score: -0.5 (/) 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 (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 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: 1WcHFo-0002jy-UN Cc: "bitcoin-development@lists.sourceforge.net" , Jonathan Levin Subject: Re: [Bitcoin-development] Economics of information propagation X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Apr 2014 16:39:40 -0000 --089e0141ab82cc46ef04f79024e2 Content-Type: text/plain; charset=UTF-8 Pieter tried it already. If the two nodes views of each others mempools are not exactly in alignment it ends up being slower than just sending the data immediately and redundantly. On Mon, Apr 21, 2014 at 6:38 PM, Mark Friedenbach wrote: > Yes, it certainly can be improved in this way. You can even extend the > idea to distribute partial proofs of work (block headers + Merkle lists > which represent significant but not sufficient work), and 'prime' your > memory pools with the transactions contained within. > > This is, btw, basically what p2pool does, which is why last time I > calculated you get roughly 1% better return from p2pool than a zero-fee > mining pool would get you, specifically because of the lower stale rate. > > On 04/21/2014 09:22 AM, Paul Lyon wrote: > > I haven't done the math on this, so it may be a terrible idea. :) > > > > I've been wondering if block propagation times could also be improved by > > allowing peers to request the list of transaction hashes that make up a > > block, and then making a follow-up request to only download any > > transactions not currently known. I'm not sure what percentage of > > transactions a node will usually already have when it receives a new > > block, but if it's high I figure this could be beneficial. > > > > > ------------------------------------------------------------------------------ > Start Your Social Network Today - Download eXo Platform > Build your Enterprise Intranet with eXo Platform Software > Java Based Open Source Intranet - Social, Extensible, Cloud Ready > Get Started Now And Turn Your Intranet Into A Collaboration Platform > http://p.sf.net/sfu/ExoPlatform > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > --089e0141ab82cc46ef04f79024e2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Pieter tried it already. If the two nodes views of each ot= hers mempools are not exactly in alignment it ends up being slower than jus= t sending the data immediately and redundantly.


On Mon, Apr 21, 2014 at 6:38 PM, Mark Fr= iedenbach <mark@monetize.io> wrote:
Yes, it certainly can be improved in this way. You can even extend the
idea to distribute partial proofs of work (block headers + Merkle lists
which represent significant but not sufficient work), and 'prime' y= our
memory pools with the transactions contained within.

This is, btw, basically what p2pool does, which is why last time I
calculated you get roughly 1% better return from p2pool than a zero-fee
mining pool would get you, specifically because of the lower stale rate.

On 04/21/2014 09:22 AM, Paul Lyon wrote:
> I haven't done the math on this, so it may be a terrible idea. :)<= br> >
> I've been wondering if block propagation times could also be impro= ved by
> allowing peers to request the list of transaction hashes that make up = a
> block, and then making a follow-up request to only download any
> transactions not currently known. I'm not sure what percentage of<= br> > transactions a node will usually already have when it receives a new > block, but if it's high I figure this could be beneficial.
>

-----------------------------= -------------------------------------------------
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.n= et/sfu/ExoPlatform
_______________________________________________
Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment

--089e0141ab82cc46ef04f79024e2--