summaryrefslogtreecommitdiff
path: root/b1/ece7f193ad0ff84fcff7e7f3275cc72da8c6f8
blob: fad9933e206663cdb9abc790ff402bb9b16a5366 (plain)
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
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
Return-Path: <rsomsen@gmail.com>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [IPv6:2605:bc80:3010::133])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 43B5AC002D
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon, 27 Jun 2022 20:35:49 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp2.osuosl.org (Postfix) with ESMTP id 1E15F4063E
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon, 27 Jun 2022 20:35:49 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 1E15F4063E
Authentication-Results: smtp2.osuosl.org;
 dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com
 header.a=rsa-sha256 header.s=20210112 header.b=RqAXJMIY
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001,
 HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001,
 SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from smtp2.osuosl.org ([127.0.0.1])
 by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id rEd0E0bBhOq7
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon, 27 Jun 2022 20:35:48 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 20C6E40289
Received: from mail-ot1-x32b.google.com (mail-ot1-x32b.google.com
 [IPv6:2607:f8b0:4864:20::32b])
 by smtp2.osuosl.org (Postfix) with ESMTPS id 20C6E40289
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon, 27 Jun 2022 20:35:47 +0000 (UTC)
Received: by mail-ot1-x32b.google.com with SMTP id
 7-20020a9d0107000000b00616935dd045so8227758otu.6
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon, 27 Jun 2022 13:35:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;
 h=mime-version:references:in-reply-to:from:date:message-id:subject:to
 :cc; bh=/HPAPglwnGLdpa5W7FxELrUBCWK9WcTERNjfp+f+hW8=;
 b=RqAXJMIYvqDoku09OpFGqrfX+QBUkFZeB1JGMLbWVVWYsUAFb8m4/hGdghfuXGIfGx
 GCsfa+XWbioQEcDwC66tYjziuwxDIqELWqAXUdQOZ0UzMuobNnMPk+DG9MGbXPC9Mria
 h2sCvfBYA1KSJcisRQioDtNl726kpDqJp9+iyWoMdZAgbycYHUVUphEKq7Qs7IOmn/BX
 OZpEKoIlPmUhXNi5Qepn+BkqeE56LWf32Juhs328/PemSILjir73+IERhJ5u9hulHJg2
 wzmZ5MJ0SXEfuasBqT1mqnZkg6q91BQxzaP+nR3N7qW4QvnXqCKlB9IPwRtexuJTVMXS
 2f3A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20210112;
 h=x-gm-message-state:mime-version:references:in-reply-to:from:date
 :message-id:subject:to:cc;
 bh=/HPAPglwnGLdpa5W7FxELrUBCWK9WcTERNjfp+f+hW8=;
 b=Do9AAmzVkto71Gx0MeNlD18QvrfrCWmvODJZ8/ASeeNcChKawh9kJTef7r/KMtaNmO
 jMUNcp0zoqfZ7EgO2TX5wlncl4rxSf6ZFeTMrtR0qNMrZi/PienjpMYKtvC37RgqPZlo
 X/zSyPU4AUjagB90T/MNcXTtx5EhiHOGm93vDr2J0qjvkevaocubDCi3HdOUkdzP58dh
 2t5+IwLmNiDWhIine17Dr5yVcYpMwhpwPzM+mdj5dBIKVzqrEPSHXDMmHf4SXMDumsVG
 ZBVZIrv9ABcNQ9uY6thQX0S+pBZo753AYjwUYUY9vgioE+b9lTGX79L5cTBKnnPwnKK/
 plIg==
X-Gm-Message-State: AJIora9n8VYGwMigmPlyEc/AeDLx6+av95rF98wAEiR5k913Mw+pPxao
 q7e3omHcutDqwAq0+y5nY3OOB5Da6Y1vyZTDfrk=
X-Google-Smtp-Source: AGRyM1sOM85q6TnMnKvR6VL5C2pIBTkQaUVgok2YiMtZlKQkJ5hOopxOs1SV0EHIylWAqwhOg+uiVR7ACU6Rn65sve0=
X-Received: by 2002:a05:6830:2783:b0:60c:1052:b67d with SMTP id
 x3-20020a056830278300b0060c1052b67dmr6893996otu.313.1656362147219; Mon, 27
 Jun 2022 13:35:47 -0700 (PDT)
MIME-Version: 1.0
References: <rH1Js_T_UWcAg9lS9NDw_Qb6Js5bgs8rPILej69BjqsEZcJZwsvHhZRilkkOQZRGXabai63hrGgbTP2Yk99ojKEN6fU6HT4TmukiafqiKjo=@protonmail.com>
 <CABaSBaxinzeVuOAmGRoVttMN9puQunZNy3MVuTxk1U3=bLrg6A@mail.gmail.com>
In-Reply-To: <CABaSBaxinzeVuOAmGRoVttMN9puQunZNy3MVuTxk1U3=bLrg6A@mail.gmail.com>
From: Ruben Somsen <rsomsen@gmail.com>
Date: Mon, 27 Jun 2022 22:35:34 +0200
Message-ID: <CAPv7TjZ265K8oTaz=qum9w-HYMp-GPawq=TNcp-e_WsPcCQAOA@mail.gmail.com>
To: Bryan Bishop <kanzure@gmail.com>, 
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="000000000000678f6a05e273ddc4"
X-Mailman-Approved-At: Mon, 27 Jun 2022 20:36:23 +0000
Subject: Re: [bitcoin-dev] [BIP proposal] Private Payments
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>, 
 <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>, 
 <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jun 2022 20:35:49 -0000

--000000000000678f6a05e273ddc4
Content-Type: text/plain; charset="UTF-8"

Hi Bryan,

>just publishing on a tor hidden service that other wallets check

The problem is that this data is critical to access the funds. By putting
it on-chain you're guaranteeing that it's always available when you restore
your funds from backup.

Cheers,
Ruben

On Mon, Jun 27, 2022 at 10:21 PM Bryan Bishop via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> Hi,
>
> On Mon, Jun 27, 2022 at 2:14 PM Alfred Hodler via bitcoin-dev <
> bitcoin-dev@lists.linuxfoundation.org> wrote:
>
>> 2. Notification transactions still exist but no longer leave a privacy
>> footprint on the blockchain. Instead, a notification transaction is simply
>> a single OP_RETURN containing a value that only Alice and Bob can
>> calculate. If Alice's notification transaction uses UTXOs not associated
>> with her identity, there is never a footprint showing that either her or
>> Bob are using private payments. If Alice uses tainted coins, only she is
>> exposed as a user of Private Payments but Bob still isn't.
>>
>
> That's a neat trick. What about not using OP_RETURN at all, and just
> publishing on a tor hidden service that other wallets check?  Alice
> wouldn't have to expose on-chain that she is a sender of a private payment.
>
> - Bryan
> https://twitter.com/kanzure
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

--000000000000678f6a05e273ddc4
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Bryan,<div><br></div><div>&gt;just publishing on a tor =
hidden service that=C2=A0other wallets check</div><div><br></div><div>The p=
roblem is that this data is critical=C2=A0to access the funds. By putting i=
t on-chain you&#39;re guaranteeing that it&#39;s always available when you =
restore your funds from backup.</div><div><br></div><div>Cheers,</div><div>=
Ruben</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"g=
mail_attr">On Mon, Jun 27, 2022 at 10:21 PM Bryan Bishop via bitcoin-dev &l=
t;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@list=
s.linuxfoundation.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,20=
4);padding-left:1ex"><div dir=3D"ltr"><div>Hi,</div><br><div class=3D"gmail=
_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jun 27, 2022 at 2:14 =
PM Alfred Hodler via bitcoin-dev &lt;<a href=3D"mailto:bitcoin-dev@lists.li=
nuxfoundation.org" target=3D"_blank">bitcoin-dev@lists.linuxfoundation.org<=
/a>&gt; wrote:</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0=
px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
2. Notification transactions still exist but no longer leave a privacy foot=
print on the blockchain. Instead, a notification transaction is simply a si=
ngle OP_RETURN containing a value that only Alice and Bob can calculate. If=
 Alice&#39;s notification transaction uses UTXOs not associated with her id=
entity, there is never a footprint showing that either her or Bob are using=
 private payments. If Alice uses tainted coins, only she is exposed as a us=
er of Private Payments but Bob still isn&#39;t.<br></blockquote><div><br>Th=
at&#39;s a neat trick. What about not using OP_RETURN at all, and just publ=
ishing on a tor hidden service that=C2=A0other wallets check?=C2=A0 Alice w=
ouldn&#39;t have to expose on-chain that she is a sender of a private payme=
nt.</div><div><br></div><div>- Bryan<br></div></div><div dir=3D"ltr"><div d=
ir=3D"ltr"><a href=3D"https://twitter.com/kanzure" target=3D"_blank">https:=
//twitter.com/kanzure</a></div></div></div>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</blockquote></div>

--000000000000678f6a05e273ddc4--