From: Pavol Rusnak <stick@satoshilabs.com>
To: SatoshiSingh <SatoshiSingh@protonmail.com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Sorting outputs of a transaction in alphabetic order to protect privacy
Date: Thu, 30 Apr 2020 14:14:28 +0200 [thread overview]
Message-ID: <CAF90Avnv5a3BfWHf3uSMUsLifn9yOOhe0ORLOFmt3F3Z1MCxMw@mail.gmail.com> (raw)
In-Reply-To: <EZm2mwXwpCKxZjSuXtNx-5icIQn6uCgvn0ch1IGUjXdSbXMNBjpcWXYseiCZSrH4auyf9CXz6KtTExFJNjMDeRhTdFvvrYKlEtVUpLDfCSI=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 943 bytes --]
https://github.com/bitcoin/bips/blob/master/bip-0069.mediawiki
--
Best Regards / S pozdravom,
Pavol "stick" Rusnak
CTO, SatoshiLabs
On Thu, Apr 30, 2020, 10:21 SatoshiSingh via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Hi list. I've been a lurker for quite sometime and this is my first post.
>
> The problem I'm addressing is that generally wallet devs construct the tx
> with the 2nd output being of the sender as change. This helps chain
> analysers to identity addresses and invade the users privacy.
>
> I'm suggesting to sort the outputs in alphabetic order (or by pure random
> order) before broadcasting. This way the chain analyser cannot be sure
> which output is the change output and will improve privacy a little.
>
> Thanks_______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
[-- Attachment #2: Type: text/html, Size: 1606 bytes --]
prev parent reply other threads:[~2020-04-30 12:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 6:47 [bitcoin-dev] Sorting outputs of a transaction in alphabetic order to protect privacy SatoshiSingh
2020-04-30 12:14 ` Pavol Rusnak [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=CAF90Avnv5a3BfWHf3uSMUsLifn9yOOhe0ORLOFmt3F3Z1MCxMw@mail.gmail.com \
--to=stick@satoshilabs.com \
--cc=SatoshiSingh@protonmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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