diff options
author | Gavin Andresen <gavinandresen@gmail.com> | 2014-12-04 11:46:28 -0500 |
---|---|---|
committer | bitcoindev <bitcoindev@gnusha.org> | 2014-12-04 16:46:35 +0000 |
commit | faa619e98af7eb845e41189df53ab21f58a9d814 (patch) | |
tree | 32d4b75dbb8e1b31ac5072acd8c64bbb31d7d208 | |
parent | 92eb430fc2620aca414d42bc818d2ac8f362690f (diff) | |
download | pi-bitcoindev-faa619e98af7eb845e41189df53ab21f58a9d814.tar.gz pi-bitcoindev-faa619e98af7eb845e41189df53ab21f58a9d814.zip |
Re: [Bitcoin-development] Serialised P2SH HD chains
-rw-r--r-- | 27/378f9c8a1d8c1aee7abf7ca32ada86bb6af82c | 127 |
1 files changed, 127 insertions, 0 deletions
diff --git a/27/378f9c8a1d8c1aee7abf7ca32ada86bb6af82c b/27/378f9c8a1d8c1aee7abf7ca32ada86bb6af82c new file mode 100644 index 000000000..0940ded79 --- /dev/null +++ b/27/378f9c8a1d8c1aee7abf7ca32ada86bb6af82c @@ -0,0 +1,127 @@ +Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] + helo=mx.sourceforge.net) + by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) + (envelope-from <gavinandresen@gmail.com>) id 1XwZY3-0003H3-5a + for bitcoin-development@lists.sourceforge.net; + Thu, 04 Dec 2014 16:46:35 +0000 +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; +Received: from mail-yh0-f54.google.com ([209.85.213.54]) + by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) + (Exim 4.76) id 1XwZY2-0005k2-0P + for bitcoin-development@lists.sourceforge.net; + Thu, 04 Dec 2014 16:46:35 +0000 +Received: by mail-yh0-f54.google.com with SMTP id 29so9011917yhl.41 + for <bitcoin-development@lists.sourceforge.net>; + Thu, 04 Dec 2014 08:46:28 -0800 (PST) +MIME-Version: 1.0 +X-Received: by 10.236.228.195 with SMTP id f63mr14042474yhq.165.1417711588546; + Thu, 04 Dec 2014 08:46:28 -0800 (PST) +Received: by 10.170.209.68 with HTTP; Thu, 4 Dec 2014 08:46:28 -0800 (PST) +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 +X-Spam-Score: 0.0 (/) +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 + (gavinandresen[at]gmail.com) + -0.0 SPF_PASS SPF: sender matches SPF record + 1.0 HTML_MESSAGE BODY: HTML included in message + -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 + 0.6 URIBL_SBL Contains an URL's NS IP listed in the SBL blocklist + [URIs: dashjr.org] +X-Headers-End: 1XwZY2-0005k2-0P +Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net> +Subject: Re: [Bitcoin-development] Serialised P2SH HD chains +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, 04 Dec 2014 16:46:35 -0000 + +--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"><<a href=3D"m= +ailto:luke@dashjr.org" target=3D"_blank">luke@dashjr.org</a>></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'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" =3D=3D "give them a recurring Paymen= +tRequest" in my mind. Or maybe "Give them a URL where they can fe= +tch PaymentRequests whenever they need to make a payment" or maybe &qu= +ot;Give them an array of PaymentRequests for the next X days/months/years o= +f payments."</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-- + + |