1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <luke@dashjr.org>) id 1XwdfP-0007Qx-29
for bitcoin-development@lists.sourceforge.net;
Thu, 04 Dec 2014 21:10:27 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of dashjr.org
designates 85.234.147.28 as permitted sender)
client-ip=85.234.147.28; envelope-from=luke@dashjr.org;
helo=zinan.dashjr.org;
Received: from 85-234-147-28.static.as29550.net ([85.234.147.28]
helo=zinan.dashjr.org)
by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1XwdfN-0005X8-Mr for bitcoin-development@lists.sourceforge.net;
Thu, 04 Dec 2014 21:10:27 +0000
Received: from ishibashi.localnet (unknown
[IPv6:2001:470:5:265:61b6:56a6:b03d:28d6])
(Authenticated sender: luke-jr)
by zinan.dashjr.org (Postfix) with ESMTPSA id EB8E7108039B;
Thu, 4 Dec 2014 21:10:17 +0000 (UTC)
From: Luke Dashjr <luke@dashjr.org>
To: Jeffrey Paul <jp@eeqj.com>
Date: Thu, 4 Dec 2014 21:10:14 +0000
User-Agent: KMail/1.13.7 (Linux/3.17.3-gentoo; KDE/4.12.5; x86_64; ; )
References: <201412041542.44207.luke@dashjr.org>
<F904F6F8-BA2E-4B86-8C6C-B34A88D384BD@eeqj.com>
In-Reply-To: <F904F6F8-BA2E-4B86-8C6C-B34A88D384BD@eeqj.com>
X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F
X-PGP-Key-ID: BD02942421F4889F
X-PGP-Keyserver: hkp://pgp.mit.edu
MIME-Version: 1.0
Content-Type: Text/Plain;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Message-Id: <201412042110.16655.luke@dashjr.org>
X-Spam-Score: -1.5 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
0.0 TVD_RCVD_IP Message was received from an IP address
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
-0.0 SPF_PASS SPF: sender matches SPF record
X-Headers-End: 1XwdfN-0005X8-Mr
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 21:10:27 -0000
On Thursday, December 04, 2014 8:02:17 PM Jeffrey Paul wrote:
> What is the use case for something like this? It=E2=80=99s my impression=
that a
> single token that can be used to obtain many P2SH addresses paying to a
> multisig script looks something like
>=20
> bitcoin:?r=3Dhttps://payee.com/customer12345/recurring/paymentrequest/=
new
This requires the payee operate a server. My use case is for payment to=20
individuals, who may or may not have a computer powered at the time of the=
=20
transactions being sent. Furthermore, the users I am targeting (miners, to =
be=20
specific), wish to remain entirely anonymous, and not hold accounts of any=
=20
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=E2=80=99 keys. Is=
this
> wise?
This depends on the framework. As of present day, miners are limited to onl=
y=20
use a single address ever, and cannot change it even to avoid address reuse=
=2E=20
One goal is to solve that, without breaking multisig.
Luke
|
