1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
|
Return-Path: <ZmnSCPxj@protonmail.com>
Received: from hemlock.osuosl.org (smtp2.osuosl.org [140.211.166.133])
by lists.linuxfoundation.org (Postfix) with ESMTP id 43782C016F
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 27 May 2020 04:12:01 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by hemlock.osuosl.org (Postfix) with ESMTP id 2C88387E93
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 27 May 2020 04:12:01 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
Received: from hemlock.osuosl.org ([127.0.0.1])
by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id JEq6+v02v-zg
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 27 May 2020 04:11:59 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from mail-40135.protonmail.ch (mail-40135.protonmail.ch
[185.70.40.135])
by hemlock.osuosl.org (Postfix) with ESMTPS id 439DE87D8E
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 27 May 2020 04:11:59 +0000 (UTC)
Date: Wed, 27 May 2020 04:11:47 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com;
s=protonmail; t=1590552717;
bh=VqqgVxSh008aBdmHAX12AM5lwhAaN8xkIJBCQi4gaJc=;
h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From;
b=kvmUGiKk9EoAkLlSg+q+Kg1Yno+jA6J6HJpKW+D5kKfSjYorVaGDs5IYz3hxyzLrt
9EM0rc8/NjvX7+B5mZiQos23EV7MOc5a/LP/mqTveNMaPdug4ho0WgH/LvUbPM+R3b
k3JbnXDFTNWOo0XpBjJwdjR7FkyraLq2QJUsmAEM=
To: Prayank <prayank@tutanota.de>
From: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Reply-To: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Message-ID: <5cRx3Q_UFKDJkF0Jc8XcZEHHwbPxc85YbGPcITRMweC9qdfhmZLT3AVdnqpej5poLdl8t2JiHyRofBD22yv_lxFlxz2J6N8eiBHsMRM_cBQ=@protonmail.com>
In-Reply-To: <M8G151E--3-2@tutanota.de>
References: <M87d6RV--3-2@tutanota.de>
<3K6kmk75oNFwNf_E4xqPgf5URJOf4c64Iyxi1HOgEpvvZrdn_wBWxbx3hRBEDfu2MjC5kF6N0ejpjqeG_5FTGIFD_45sFyhLCtMvhJNdq3E=@protonmail.com>
<M8AkjX3--3-2@tutanota.de>
<jrsxyefXxsLMundu38HnLPf8f_SnedDldcopEiFUZj0A4rsdm6NtdkNQsI3fvUd34Nf2LcLt1vnv5aAJR2bmY4keM69Xsu0uoIng2ILh9t4=@protonmail.com>
<M8G151E--3-2@tutanota.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
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
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Wed, 27 May 2020 04:12:01 -0000
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 c=
onsider 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 thi=
ngs like Peer 1 locking some amount in a 2 of 2 multisig with Peer 2 or som=
e 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 transac=
tions 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 impor=
tant 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 spend=
s coins from its wallet*.
That means that what I am describing is *how JoinMarket performs spends aft=
er mixing, i.e. post-mix*.
I was not describing how JoinMarket performs mixing.
Is that clearer now?
Regards,
ZmnSCPxj
|
