From: Gavin Andresen <gavinandresen@gmail•com>
To: Luke Dashjr <luke@dashjr•org>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Serialised P2SH HD chains
Date: Thu, 4 Dec 2014 11:46:28 -0500 [thread overview]
Message-ID: <CABsx9T0rS0R-tGHpBajPrRjtu77Z97+nhSLuWsXshHiQp4SqWg@mail.gmail.com> (raw)
In-Reply-To: <201412041542.44207.luke@dashjr.org>
[-- Attachment #1: Type: text/plain, Size: 1040 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 1927 bytes --]
next prev parent reply other threads:[~2014-12-04 16:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 15:42 Luke Dashjr
2014-12-04 16:46 ` Gavin Andresen [this message]
2014-12-04 17:25 ` William Swanson
2014-12-04 18:04 ` Mike Hearn
2014-12-04 20:02 ` Jeffrey Paul
2014-12-04 20:43 ` Peter Todd
2014-12-04 21:10 ` Luke Dashjr
[not found] <mailman.473107.1417725057.2207.bitcoin-development@lists.sourceforge.net>
2014-12-04 20:40 ` Michael Perklin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CABsx9T0rS0R-tGHpBajPrRjtu77Z97+nhSLuWsXshHiQp4SqWg@mail.gmail.com \
--to=gavinandresen@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=luke@dashjr$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox