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
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <ctpacia@gmail.com>) id 1Xqt9F-0006IL-PZ
for bitcoin-development@lists.sourceforge.net;
Wed, 19 Nov 2014 00:29:29 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.218.43 as permitted sender)
client-ip=209.85.218.43; envelope-from=ctpacia@gmail.com;
helo=mail-oi0-f43.google.com;
Received: from mail-oi0-f43.google.com ([209.85.218.43])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Xqt9D-0003nJ-Dt
for bitcoin-development@lists.sourceforge.net;
Wed, 19 Nov 2014 00:29:29 +0000
Received: by mail-oi0-f43.google.com with SMTP id a3so6811530oib.16
for <bitcoin-development@lists.sourceforge.net>;
Tue, 18 Nov 2014 16:29:22 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.202.227.73 with SMTP id a70mr9992313oih.59.1416349992842;
Tue, 18 Nov 2014 14:33:12 -0800 (PST)
Received: by 10.60.155.103 with HTTP; Tue, 18 Nov 2014 14:33:12 -0800 (PST)
Received: by 10.60.155.103 with HTTP; Tue, 18 Nov 2014 14:33:12 -0800 (PST)
In-Reply-To: <CAPg+sBh0dnU9DtcP=PYzC9fmMbjzcEfYZw8exHwxfDcF3FcFtA@mail.gmail.com>
References: <CABbpET9eTgk1GyxYbcG++O_rqsnfB7w5_Xp4XgE6qwkmGsm1eg@mail.gmail.com>
<201411161724.19573.luke@dashjr.org>
<CABm2gDpBOtZB01Qj3Dc3dWSpG2zLr+VPYbnwrq8YVh8qfxMW5Q@mail.gmail.com>
<CABm2gDoi1593ssoGN69E42c-N3s02yYKAqDEDA2m-e+6LqjpTQ@mail.gmail.com>
<5469692F.9030702@gmail.com>
<CAPg+sBgM4ja0Y96KekJUN7Qg=o0xa1B0VUiiPuFQTYfrupoERg@mail.gmail.com>
<CALqxMTH3qBU88xpSu_evuBfRwMmF3cLpM=L5DUExKc--cO_O1Q@mail.gmail.com>
<5469EAA5.1020606@gmail.com>
<CAPg+sBh0dnU9DtcP=PYzC9fmMbjzcEfYZw8exHwxfDcF3FcFtA@mail.gmail.com>
Date: Tue, 18 Nov 2014 17:33:12 -0500
Message-ID: <CAB+qUq6+hDvDMm=E1nw300AWS_RvdLgHZofgddPzZCxPmgWTnQ@mail.gmail.com>
From: Chris Pacia <ctpacia@gmail.com>
To: Pieter Wuille <pieter.wuille@gmail.com>
Content-Type: multipart/alternative; boundary=001a114093d2337c92050829ae85
X-Spam-Score: -0.6 (/)
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
(ctpacia[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
X-Headers-End: 1Xqt9D-0003nJ-Dt
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Increasing the OP_RETURN maximum payload
size
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: Wed, 19 Nov 2014 00:29:30 -0000
--001a114093d2337c92050829ae85
Content-Type: text/plain; charset=UTF-8
On Nov 17, 2014 7:39 AM, "Pieter Wuille" <pieter.wuille@gmail.com> wrote:
> That is inevitable for any wallet that offers any functionality beyond
> just maintaining a balance and the ability to send coins. In
> particular, anything that wishes to list previous transaction (with
> timestamps, history, metadata, messages sent using t
> What HD wallets (or any type of deterministic derivation scheme) offer
> is the fact that you can separate secret data and public data. You
> only need one safe backup of the master secret key - all the rest can
> at most result in privacy loss and not in lost coins.
>
> --
> Pieter
I agree but right now wallets not using stealth will only lose metadata,
not coins, if their computer crashes and they have the seed backed up.
But if a user wants to upgrade to stealth, they then risk losing metadata
AND coins if they either didn't manually back up after every transaction or
use a centralized cloud backup service.
That's if OP_RETURN is not utilized for storage.
--001a114093d2337c92050829ae85
Content-Type: text/html; charset=UTF-8
<p dir="ltr"><br>
On Nov 17, 2014 7:39 AM, "Pieter Wuille" <<a href="mailto:pieter.wuille@gmail.com">pieter.wuille@gmail.com</a>> wrote:</p>
<p dir="ltr">> That is inevitable for any wallet that offers any functionality beyond<br>
> just maintaining a balance and the ability to send coins. In<br>
> particular, anything that wishes to list previous transaction (with<br>
> timestamps, history, metadata, messages sent using t<br>
> What HD wallets (or any type of deterministic derivation scheme) offer<br>
> is the fact that you can separate secret data and public data. You<br>
> only need one safe backup of the master secret key - all the rest can<br>
> at most result in privacy loss and not in lost coins.<br>
><br>
> --<br>
> Pieter</p>
<p dir="ltr">I agree but right now wallets not using stealth will only lose metadata, not coins, if their computer crashes and they have the seed backed up. </p>
<p dir="ltr">But if a user wants to upgrade to stealth, they then risk losing metadata AND coins if they either didn't manually back up after every transaction or use a centralized cloud backup service.</p>
<p dir="ltr">That's if OP_RETURN is not utilized for storage. </p>
--001a114093d2337c92050829ae85--
|
