From: Ruben Somsen <rsomsen@gmail•com>
To: Bryan Bishop <kanzure@gmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] [BIP proposal] Private Payments
Date: Mon, 27 Jun 2022 22:35:34 +0200 [thread overview]
Message-ID: <CAPv7TjZ265K8oTaz=qum9w-HYMp-GPawq=TNcp-e_WsPcCQAOA@mail.gmail.com> (raw)
In-Reply-To: <CABaSBaxinzeVuOAmGRoVttMN9puQunZNy3MVuTxk1U3=bLrg6A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1464 bytes --]
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
>
[-- Attachment #2: Type: text/html, Size: 2488 bytes --]
next prev parent reply other threads:[~2022-06-27 20:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 18:17 Alfred Hodler
2022-06-27 20:20 ` Bryan Bishop
2022-06-27 20:35 ` Ruben Somsen [this message]
2022-06-28 12:40 ` Alfred Hodler
2022-06-27 20:30 ` Ruben Somsen
2022-06-28 12:35 ` Alfred Hodler
[not found] ` <PS2P216MB10894F1EE83AFA648003C6339DBF9@PS2P216MB1089.KORP216.PROD.OUTLOOK.COM>
2022-07-05 9:38 ` Alfred Hodler
2022-06-28 23:33 ` Peter Todd
2022-06-29 22:33 ` Clark Moody
2022-07-01 12:41 ` Alfred Hodler
2022-07-01 17:37 ` Christopher Allen
2022-07-11 10:28 ` Alfred Hodler
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='CAPv7TjZ265K8oTaz=qum9w-HYMp-GPawq=TNcp-e_WsPcCQAOA@mail.gmail.com' \
--to=rsomsen@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=kanzure@gmail$(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