blob: c263a7936c39eb04eab0ecef4062382a13efd1d1 (
plain)
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
99
100
101
102
103
104
105
106
107
108
109
110
111
112
|
Return-Path: <prayank@tutanota.de>
Received: from silver.osuosl.org (smtp3.osuosl.org [140.211.166.136])
by lists.linuxfoundation.org (Postfix) with ESMTP id 77909C016F
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 24 May 2020 21:50:37 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by silver.osuosl.org (Postfix) with ESMTP id 53D0421544
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 24 May 2020 21:50:37 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
Received: from silver.osuosl.org ([127.0.0.1])
by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id HWZ9iRMdqWjp
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 24 May 2020 21:50:35 +0000 (UTC)
X-Greylist: delayed 00:06:05 by SQLgrey-1.7.6
Received: from w1.tutanota.de (w1.tutanota.de [81.3.6.162])
by silver.osuosl.org (Postfix) with ESMTPS id 355FB2043A
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 24 May 2020 21:50:34 +0000 (UTC)
Received: from w3.tutanota.de (unknown [192.168.1.164])
by w1.tutanota.de (Postfix) with ESMTP id AADF2FA056C
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 24 May 2020 21:44:27 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1590356667;
s=s1; d=tutanota.de;
h=From:From:To:To:Subject:Subject:Content-Description:Content-ID:Content-Type:Content-Type:Content-Transfer-Encoding:Cc:Date:Date:In-Reply-To:MIME-Version:MIME-Version:Message-ID:Message-ID:Reply-To:References:Sender;
bh=od9FMCpOVvXP/7WizB/Ji9f12x0Jffy6GXDjYMXsj/Y=;
b=MY8jRBj0Bsue1dZZu+nAo5zTz7Sbg/763U3KDghi/9TqzF2wUgmD3PL5h6D3dzkA
kC4YeJXzhNH4j46Z/22Kc0R4VHfqGEF3W42Jl/CUrSiMzjpeXyITXS0Xz2FjouN+Gtf
3k7hPhuuQsVFEEH8zWdJgl+AR/PLzd9ggDJzhWYI5iPX+kLVpmHRya+59pzRWClKhhO
lNwzuzhboDT+65mLBmqIy1Xn819G/vGapgXQyi4S7xmFSG9qXfZ9a6WLqvcklKyp1jF
S51wRXNOCMDTX2+XxFWde+sB3bkkBbeufWwu/AULlFCccWFTYRe8EA6PLTepbcoha4G
UwN2dWaqYQ==
Date: Sun, 24 May 2020 23:44:27 +0200 (CEST)
From: prayank@tutanota.de
To: bitcoin-dev@lists.linuxfoundation.org
Message-ID: <M87d6RV--3-2@tutanota.de>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_Part_68088_655160920.1590356667683"
X-Mailman-Approved-At: Sun, 24 May 2020 23:55:19 +0000
Subject: [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: Sun, 24 May 2020 21:50:37 -0000
------=_Part_68088_655160920.1590356667683
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
I have explained the whole idea with a proof of concept in this link:=C2=A0=
https://medium.com/@prayankgahlot/post-mix-usage-using-multisig-and-cpfp-e6=
ce1fdd57a1
Does it make sense to add such options in bitcoin core wallet and how is th=
e overall idea once we have taproot because for now people can check if the=
tx involves a multisig address?
Reading Peter Wuille's reply here it seems taproot will improve privacy for=
multisig:=C2=A0
https://www.reddit.com/r/Bitcoin/comments/etagx4/please_explain_taproot_and=
_schnorr_signatures/fffljnl/
Looking for some feedback to work on this idea and don't want it to just re=
main an article on medium.=C2=A0
Thanks
Prayank
------=_Part_68088_655160920.1590356667683
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<meta http-equiv=3D"content-type" content=3D"text/html; charset=3DUTF-8=
">
</head>
<body>
<div><div>I have explained the whole idea with a proof of concept in this l=
ink: <a href=3D"https://medium.com/@prayankgahlot/post-mix-usage-using=
-multisig-and-cpfp-e6ce1fdd57a1" rel=3D"noopener noreferrer" target=3D"_bla=
nk">https://medium.com/@prayankgahlot/post-mix-usage-using-multisig-and-cpf=
p-e6ce1fdd57a1</a><br></div><div><br></div><div>Does it make sense to add s=
uch options in bitcoin core wallet and how is the overall idea once we have=
taproot because for now people can check if the tx involves a multisig add=
ress?<br></div><div><br></div><div>Reading Peter Wuille's reply here it see=
ms taproot will improve privacy for multisig: <br></div><div><a href=
=3D"https://www.reddit.com/r/Bitcoin/comments/etagx4/please_explain_taproot=
_and_schnorr_signatures/fffljnl/" rel=3D"noopener noreferrer" target=3D"_bl=
ank">https://www.reddit.com/r/Bitcoin/comments/etagx4/please_explain_taproo=
t_and_schnorr_signatures/fffljnl/</a><br></div><div><br></div><div>Looking =
for some feedback to work on this idea and don't want it to just remain an =
article on medium. <br></div><div><br></div><div>Thanks<br></div><div>=
<br></div><div>Prayank<br></div></div><div><br></div> </body>
</html>
------=_Part_68088_655160920.1590356667683--
|
