From: Alfred Hodler <alfred_hodler@protonmail•com>
To: Ruben Somsen <rsomsen@gmail•com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] New BIP: Private Payments
Date: Mon, 01 Aug 2022 11:38:29 +0000 [thread overview]
Message-ID: <as1OIZRWFJz8-hXljBG0Y9urM8C9eLBfmM7cEdXQyQyvDDmOyMDM4Tp2-EgvpcgI1ysv1LKT5c7R68WXrhPsq5403AtBk8nMFX3USkxD5l0=@protonmail.com> (raw)
In-Reply-To: <CAPv7TjZHJoY2cN9=X7vxSOEbd-YLQLrFi87e8Yj-xZJUawjRYA@mail.gmail.com>
Hi Ruben,
I have incorporated your feedback. Using only the first four bytes of the notification code is a very valuable suggestion, so thank you for that. I have added you as a co-author.
In regards to hiding the recipient in the notification, the purpose is not only to allow Alice to send a notification herself, but also to break the link between the notifier (be that Alice or a third-party service) and Bob. Not doing so would reintroduce the same problem we have with BIP47 and unique per-recipient notification addresses -- namely that of social graph building. The tradeoff, as you noticed, is that light clients have to rely on some kind of OP_RETURN indexing service. I personally consider any inconvenience (to developers, as end users never see this) stemming from that to be acceptable because:
1) it reduces the amount of social metadata on the blockchain
2) notification services might otherwise be pressured into censoring certain recipients
3) it allows wallets to decide the level of outsourcing they are comfortable with
4) adversaries monitoring notifications might see a lot of notifications to someone and use that information to mount an attack
Thanks for all the feedback.
Alfred
prev parent reply other threads:[~2022-08-01 11:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-30 9:24 Alfred Hodler
2022-07-30 13:41 ` Ruben Somsen
2022-08-01 11:38 ` Alfred Hodler [this message]
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='as1OIZRWFJz8-hXljBG0Y9urM8C9eLBfmM7cEdXQyQyvDDmOyMDM4Tp2-EgvpcgI1ysv1LKT5c7R68WXrhPsq5403AtBk8nMFX3USkxD5l0=@protonmail.com' \
--to=alfred_hodler@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=rsomsen@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