From: ZmnSCPxj <ZmnSCPxj@protonmail•com>
To: Prayank <prayank@tutanota•de>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Post-mix(coinjoin) usage with multisig and cpfp in bitcoin core wallet
Date: Wed, 27 May 2020 04:11:47 +0000 [thread overview]
Message-ID: <5cRx3Q_UFKDJkF0Jc8XcZEHHwbPxc85YbGPcITRMweC9qdfhmZLT3AVdnqpej5poLdl8t2JiHyRofBD22yv_lxFlxz2J6N8eiBHsMRM_cBQ=@protonmail.com> (raw)
In-Reply-To: <M8G151E--3-2@tutanota.de>
Good morning Prayank,
> 1. The spending tx of multisig can be decided earlier and all three can review the outputs involved in it. All 3 txs involved in the system if we consider only one mixer and not a chain will get confirmed in the same block as we are using CPFP so child pays for 2 parent txs. However, disputes are possible and to manage it we will have to make the system complex with things like Peer 1 locking some amount in a 2 of 2 multisig with Peer 2 or some other incentives structure. Initially we can try to keep it simple and a way to spend coins after coinjoin with the help of another person you trust.
The payee is not necessary here and you can remove the intermediate transactions that pay to 2-of-3s.
> 2. Yes, you described coinjoin in joinmarket but the problem I am trying to solve is: spend coins after coinjoin because post-mix usage is as important as coinjoin. Some users dont follow the best practices after coinjoin and it makes coinjoin useless or less effective in that case and sometimes for others involved in the process as well.
...
I already mentioned this, but what I am describing is *how JoinMarket spends coins from its wallet*.
That means that what I am describing is *how JoinMarket performs spends after mixing, i.e. post-mix*.
I was not describing how JoinMarket performs mixing.
Is that clearer now?
Regards,
ZmnSCPxj
prev parent reply other threads:[~2020-05-27 4:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-24 21:44 prayank
2020-05-25 6:54 ` ZmnSCPxj
2020-05-25 12:16 ` prayank
2020-05-26 2:46 ` ZmnSCPxj
2020-05-26 12:50 ` Prayank
2020-05-27 4:11 ` ZmnSCPxj [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='5cRx3Q_UFKDJkF0Jc8XcZEHHwbPxc85YbGPcITRMweC9qdfhmZLT3AVdnqpej5poLdl8t2JiHyRofBD22yv_lxFlxz2J6N8eiBHsMRM_cBQ=@protonmail.com' \
--to=zmnscpxj@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=prayank@tutanota$(echo .)de \
/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