From: Max Hillebrand <max@towardsliberty•com>
To: alicexbt <alicexbt@protonmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>,
alicexbt via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] joinstr: coinjoin implementation using nostr
Date: Sat, 20 Aug 2022 12:04:11 +0200 [thread overview]
Message-ID: <11A4C398-8CEA-4FDF-B450-55649E6CA1FF@pretty.Easy.privacy> (raw)
In-Reply-To: <7gXWd6OVJjiW7aCeon8q-xlWfCMJkIEVCaeokjSVI16OvQPkPmEsSeGY0cGu4yVveimNUYsyG18Ro7JgUutfqXv5wKMMgJZD2c8ftAMFcbQ=@protonmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 612 bytes --]
Great to see an implementation of the idea.
Maybe I misunderstand, but isn't there a vulnerability of denial of service here?
A user who registers one input will receive the round secret identifier, and this is all the information required for output registration. However, that malicious user can now register multiple outputs, providing the same secret, and nobody can link the malicious outputs to any specific input. Therefor there cannot be a blame round where the malicious input is removed, and thus there can be a ongoing free denial of service attack without attribution or defense.
Skol
Max
[-- Attachment #1.2: Type: text/html, Size: 6716 bytes --]
[-- Attachment #2: sender_key.asc --]
[-- Type: application/pgp-keys, Size: 3910 bytes --]
next prev parent reply other threads:[~2022-08-20 10:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-20 8:20 alicexbt
2022-08-20 10:04 ` Max Hillebrand [this message]
2022-08-20 16:52 alicexbt
2022-09-09 21:05 ` woltx
2022-09-10 10:17 ` alicexbt
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=11A4C398-8CEA-4FDF-B450-55649E6CA1FF@pretty.Easy.privacy \
--to=max@towardsliberty$(echo .)com \
--cc=alicexbt@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.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