From: Luke Dashjr <luke@dashjr•org>
To: Jeffrey Paul <jp@eeqj•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Serialised P2SH HD chains
Date: Thu, 4 Dec 2014 21:10:14 +0000 [thread overview]
Message-ID: <201412042110.16655.luke@dashjr.org> (raw)
In-Reply-To: <F904F6F8-BA2E-4B86-8C6C-B34A88D384BD@eeqj.com>
On Thursday, December 04, 2014 8:02:17 PM Jeffrey Paul wrote:
> What is the use case for something like this? It’s my impression that a
> single token that can be used to obtain many P2SH addresses paying to a
> multisig script looks something like
>
> bitcoin:?r=https://payee.com/customer12345/recurring/paymentrequest/new
This requires the payee operate a server. My use case is for payment to
individuals, who may or may not have a computer powered at the time of the
transactions being sent. Furthermore, the users I am targeting (miners, to be
specific), wish to remain entirely anonymous, and not hold accounts of any
sort.
> The model that you describe where a payer can, without communication with
> the payee, generate additional multisig p2sh addresses based on a set of
> xpubs presumes that the payee would never want to e.g. cycle their own
> keys or change their cooperating multisig participants’ keys. Is this
> wise?
This depends on the framework. As of present day, miners are limited to only
use a single address ever, and cannot change it even to avoid address reuse.
One goal is to solve that, without breaking multisig.
Luke
next prev parent reply other threads:[~2014-12-04 21:10 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
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 [this message]
[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=201412042110.16655.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jp@eeqj$(echo .)com \
/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