From: Yuval Kogman <nothingmuch@woobling•org>
To: Peter Todd <pete@petertodd•org>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Reiterating centralized coinjoin (Wasabi & Samourai) deanonymization attacks
Date: Fri, 4 Apr 2025 19:58:37 +0200 [thread overview]
Message-ID: <CAAQdECAXTJ6fP8PBYmJdZeggKxJRWvcEPW9UCZ4w8_K7A3+mCA@mail.gmail.com> (raw)
In-Reply-To: <Z_AMBe7CnGX_Rm14@petertodd.org>
That's 3 months after Kruw'd coordinator started operating, 2 months
after his podcast appearance which I linked to, and 7 months after the
change was merged despite NACKs, as I have already stated in the very
same email you are quoting:
> During most of the zksnack's coordinator run, that surplus went
> towards *mining* fees, and was widely understood to do so. This part
> is entirely server side policy, and possible due to gaps in the
> protocol and the client implementation. The coordinator software was
> modified to claim those excess mining fees with no justification of
> overruling cNACK that had led to it being not merged 6 months prior
> https://github.com/WalletWasabi/WalletWasabi/pull/10884#pullrequestreview-1485776991
> and that was only publicly documented around 7 months later, after the
> zksnacks coordinator shutdown and the removal of explicit coordinator
> fees https://github.com/WalletWasabi/WasabiDoc/pull/1841/files and
> only fully clarified a month after that
> https://github.com/WalletWasabi/WasabiDoc/pull/1859
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups•com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/CAAQdECAXTJ6fP8PBYmJdZeggKxJRWvcEPW9UCZ4w8_K7A3%2BmCA%40mail.gmail.com.
next prev parent reply other threads:[~2025-04-07 10:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-21 14:16 Yuval Kogman
2025-01-06 13:07 ` Sjors Provoost
2025-01-06 14:30 ` Yuval Kogman
2025-01-07 15:56 ` waxwing/ AdamISZ
2025-01-07 21:33 ` Yuval Kogman
2025-01-23 16:25 ` Peter Todd
2025-01-24 16:00 ` Peter Todd
2025-01-24 16:38 ` waxwing/ AdamISZ
2025-02-04 14:02 ` Yuval Kogman
2025-02-04 22:22 ` Peter Todd
2025-02-07 20:07 ` Yuval Kogman
[not found] ` <sqPb0Ljo2YteBE3rTHUfnrdHihbV9UnZjM4Q7tfqYzDuqsGZbHcaqJnU9LYwN7_iaqIO9B-FVAx3aXRyuDh1TnzZ-Mnp_2vRC4JblnvN1O4=@protonmail.com>
2025-02-13 15:42 ` Yuval Kogman
2025-02-12 10:17 ` /dev /fd0
[not found] ` <CAAQdECD9MfVqU=BLgRpUnEMa=m0cnGj4SWCcviKzpRYJktMaNA@mail.gmail.com>
2025-04-04 16:42 ` Peter Todd
2025-04-04 17:58 ` Yuval Kogman [this message]
2025-04-04 19:59 ` Yuval Kogman
2025-04-07 10:01 ` Javier Mateos
2025-04-09 2:16 ` Yuval Kogman
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=CAAQdECAXTJ6fP8PBYmJdZeggKxJRWvcEPW9UCZ4w8_K7A3+mCA@mail.gmail.com \
--to=nothingmuch@woobling$(echo .)org \
--cc=bitcoindev@googlegroups.com \
--cc=pete@petertodd$(echo .)org \
/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