Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.219.53 as permitted sender)
	client-ip=209.85.219.53; envelope-from=mh.in.england@gmail.com;
	helo=mail-oa0-f53.google.com; 
MIME-Version: 1.0
Sender: mh.in.england@gmail.com
In-Reply-To: <20130816145912.GA16533@petertodd.org>
References: <CABsx9T32q8mKgtmsaZgh7nuhHY5cExeW=FiadzXq3jXVP=NBTw@mail.gmail.com>
	<CANEZrP0PEcP339MKRyrHXHCCsP3BxRHT-ZfKRQ7G2Ou+15CD7A@mail.gmail.com>
	<CANEZrP3LAR0erjgmTHruLwPNDdx-OVyb9KK52E6UnmE4ZuBrvQ@mail.gmail.com>
	<20130816140116.GB16201@petertodd.org>
	<20130816141536.GD16201@petertodd.org>
	<CAEz79PoK9u9ffJ5jR8yXk8eCFP0Ytk_bno0mpcpM24mt-GGg5w@mail.gmail.com>
	<CANEZrP3hHh3k5+ePGbqVeyo3oV=RTy36FA+8MbOZXg3yMqRxAw@mail.gmail.com>
	<20130816145912.GA16533@petertodd.org>
Date: Fri, 16 Aug 2013 17:11:35 +0200
Message-ID: <CANEZrP3wzMi3oWcwCt-GEs1cXdNa0mzvso_d3htJxaahiewaYw@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Peter Todd <pete@petertodd.org>
Content-Type: multipart/alternative; boundary=089e01633baaae915204e41201bf
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Gavin's post-0.9 TODO list...
Precedence: list

--089e01633baaae915204e41201bf
Content-Type: text/plain; charset=UTF-8

On Fri, Aug 16, 2013 at 4:59 PM, Peter Todd <pete@petertodd.org> wrote:

> UPNP seems to work well for the reference client. What's the situation
> there on Android?
>

Not sure - it could be investigated. I think UPNP is an entirely
userspace-implementable protocol, so in theory it could be done by a
userspace library (even libminiupnp - java is not a requirement on android)


> I leave my phone plugged in and connected via wifi for most of the day;
> lots of people do that.
>

I suspect you mean "I think lots of people do that". I'm not so sure. We
could potentially run an experiment in the Android app to measure how many
users are in a position to contribute back, but just because you have wifi
doesn't mean you can reconfigure it using UPnP. That helps a lot in home
networks, but at the office it doesn't help.

I'm wary of a ton of work being put in to achieve not very much here.
Satoshi's original vision was always that millions of users were supported
by 100,000 or so nodes. I don't think that's unreasonable over the long
term.

Besides, prioritisation isn't very hard. Nodes can just hand clients a
signed timestamp which they remember. When re-connecting, the signed
timestamp is handed back to the node and it gives priority to those with
old timestamps. No state is required on the node side. Signing and checking
can be passed onto the general ECDSA thread pool that works its way through
pending signature operations, they'd be prioritised lower than checking
blocks/broadcasts.

--089e01633baaae915204e41201bf
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Fri, Aug 16, 2013 at 4:59 PM, Peter Todd <span dir=3D"l=
tr">&lt;<a href=3D"mailto:pete@petertodd.org" target=3D"_blank">pete@petert=
odd.org</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"g=
mail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im"><span style=3D"color:rgb(3=
4,34,34)">UPNP seems to work well for the reference client. What&#39;s the =
situation</span><br>
</div>
there on Android?<br></blockquote><div><br></div><div>Not sure - it could b=
e investigated. I think UPNP is an entirely userspace-implementable protoco=
l, so in theory it could be done by a userspace library (even libminiupnp -=
 java is not a requirement on android)</div>
<div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex">I leave my phone plugged in=
 and connected via wifi for most of the day;<br>
lots of people do that.<br></blockquote><div><br></div><div>I suspect you m=
ean &quot;I think lots of people do that&quot;. I&#39;m not so sure. We cou=
ld potentially run an experiment in the Android app to measure how many use=
rs are in a position to contribute back, but just because you have wifi doe=
sn&#39;t mean you can reconfigure it using UPnP. That helps a lot in home n=
etworks, but at the office it doesn&#39;t help.</div>
<div><br></div><div>I&#39;m wary of a ton of work being put in to achieve n=
ot very much here. Satoshi&#39;s original vision was always that millions o=
f users were supported by 100,000 or so nodes. I don&#39;t think that&#39;s=
 unreasonable over the long term.</div>
<div><br></div><div>Besides, prioritisation isn&#39;t very hard. Nodes can =
just hand clients a signed timestamp which they remember. When re-connectin=
g, the signed timestamp is handed back to the node and it gives priority to=
 those with old timestamps. No state is required on the node side. Signing =
and checking can be passed onto the general ECDSA thread pool that works it=
s way through pending signature operations, they&#39;d be prioritised lower=
 than checking blocks/broadcasts.</div>
<div><br></div></div></div></div>

--089e01633baaae915204e41201bf--