Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.213.54 as permitted sender)
	client-ip=209.85.213.54; envelope-from=gavinandresen@gmail.com;
	helo=mail-yh0-f54.google.com; 
MIME-Version: 1.0
In-Reply-To: <201412041542.44207.luke@dashjr.org>
References: <201412041542.44207.luke@dashjr.org>
Date: Thu, 4 Dec 2014 11:46:28 -0500
Message-ID: <CABsx9T0rS0R-tGHpBajPrRjtu77Z97+nhSLuWsXshHiQp4SqWg@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Luke Dashjr <luke@dashjr.org>
Content-Type: multipart/alternative; boundary=001a11c3be32a11f05050966b36f
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Serialised P2SH HD chains
Precedence: list

--001a11c3be32a11f05050966b36f
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Dec 4, 2014 at 10:42 AM, Luke Dashjr <luke@dashjr.org> wrote:

> Is anyone working on a serialisation format to convey P2SH HD chains? For example,
> to give someone who wants to make recurring payments a single token that
> can be used to generate many P2SH addresses paying to a multisig script.


Seems like the wrong approach to me, because in practice you really need
a reasonable expiration date or some way of determining that whatever you
are paying
is still around (I still get random transactions to the Bitcoin Faucet's
old addresses).

See the discussion from January about extending the payment protocol for
recurring transactions:

https://www.mail-archive.com/bitcoin-development@lists.sourceforge.net/msg03823.html

"Give them a single token" == "give them a recurring PaymentRequest" in my
mind. Or maybe "Give them a URL where they can fetch PaymentRequests
whenever they need to make a payment" or maybe "Give them an array of
PaymentRequests for the next X days/months/years of payments."

-- 
--
Gavin Andresen

--001a11c3be32a11f05050966b36f
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Dec 4, 2014 at 10:42 AM, Luke Dashjr <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:luke@dashjr.org" target=3D"_blank">luke@dashjr.org</a>&gt;</span> wro=
te:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;=
border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:=
solid;padding-left:1ex">Is anyone working on a serialisation format to conv=
ey P2SH HD chains?=A0<span style=3D"font-family:arial,sans-serif;font-size:=
13px">For=A0</span><span style=3D"font-family:arial,sans-serif;font-size:13=
px">example, to give someone who wants to make recurring payments a single =
token=A0</span><span style=3D"font-family:arial,sans-serif;font-size:13px">=
that can be used to generate many P2SH addresses paying to a multisig scrip=
t.</span></blockquote><div><br></div><div>Seems like the wrong approach to =
me, because in practice you really need</div><div>a reasonable expiration d=
ate or some way of determining that whatever you are paying</div><div>is st=
ill around (I still get random transactions to the Bitcoin Faucet&#39;s old=
 addresses).</div><div><br></div><div>See the discussion from January about=
 extending the payment protocol for</div><div>recurring transactions:</div>=
<div>=A0=A0<a href=3D"https://www.mail-archive.com/bitcoin-development@list=
s.sourceforge.net/msg03823.html">https://www.mail-archive.com/bitcoin-devel=
opment@lists.sourceforge.net/msg03823.html</a></div><div><br></div><div>&qu=
ot;Give them a single token&quot; =3D=3D &quot;give them a recurring Paymen=
tRequest&quot; in my mind. Or maybe &quot;Give them a URL where they can fe=
tch PaymentRequests whenever they need to make a payment&quot; or maybe &qu=
ot;Give them an array of PaymentRequests for the next X days/months/years o=
f payments.&quot;</div><div><br></div></div>-- <br><div class=3D"gmail_sign=
ature">--<br>Gavin Andresen<br></div><div class=3D"gmail_signature"><br></d=
iv>
</div></div>

--001a11c3be32a11f05050966b36f--