From: rhavar@protonmail.com
To: James MacWhyte <keatonatron@gmail.com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] bustapay BIP :: a practical sender/receiver coinjoin protocol
Date: Sun, 27 Jan 2019 22:11:47 +0000 [thread overview]
Message-ID: <MN5bgFMThBJ_6HiuX-aC9lAp7ainm0vhzOFMYefU-Z2QI26RUE7EmW0xTgvnxArriD-lQUTaB_wBZyKga1po6hquh1fVH5N_5wuLVIEIBfQ=@protonmail.com> (raw)
In-Reply-To: <CAH+Axy7SJhTskrTX_i+Nc+HMtcNXhOFuGi11X=EjFEfBW=H06A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 513 bytes --]
> Why does the template transaction need to be signed in step one and passed back and forth so many times? What is wrong with:
It isn't passed "back and forth so many times". It works exactly as you proposed, with the only difference is in "Step 1" the sender uses a *signed* transaction instead of an unsigned one. This is an important anti-DoS/anti-spy tactic, as it proves the sender actually owns those inputs and if the protocol is not followed to completion, the transaction can be dumped on the network.
[-- Attachment #2: Type: text/html, Size: 675 bytes --]
next prev parent reply other threads:[~2019-01-27 22:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 20:24 [bitcoin-dev] bustapay BIP :: a practical sender/receiver coinjoin protocol rhavar
2018-09-10 12:30 ` Sjors Provoost
2018-09-10 15:49 ` rhavar
2019-01-25 14:47 ` Adam Gibson
2019-01-27 7:36 ` rhavar
2019-01-27 12:20 ` Adam Gibson
2019-01-27 19:24 ` rhavar
2019-01-27 19:42 ` James MacWhyte
2019-01-27 22:11 ` rhavar [this message]
2019-01-30 2:06 ` James MacWhyte
2019-01-30 2:46 ` rhavar
2019-01-30 20:58 ` James MacWhyte
2019-01-28 4:14 ` ZmnSCPxj
2019-01-28 13:19 ` Adam Gibson
2019-01-30 8:34 ` ZmnSCPxj
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='MN5bgFMThBJ_6HiuX-aC9lAp7ainm0vhzOFMYefU-Z2QI26RUE7EmW0xTgvnxArriD-lQUTaB_wBZyKga1po6hquh1fVH5N_5wuLVIEIBfQ=@protonmail.com' \
--to=rhavar@protonmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=keatonatron@gmail.com \
/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