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
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
|
Return-Path: <prayank@tutanota.de>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133])
by lists.linuxfoundation.org (Postfix) with ESMTP id D8915C002F
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 18 Jan 2022 22:20:48 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp2.osuosl.org (Postfix) with ESMTP id CD2E040159
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 18 Jan 2022 22:20:48 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001,
RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001,
SPF_HELO_PASS=-0.001, SPF_PASS=-0.001]
autolearn=ham autolearn_force=no
Authentication-Results: smtp2.osuosl.org (amavisd-new);
dkim=pass (2048-bit key) header.d=tutanota.de
Received: from smtp2.osuosl.org ([127.0.0.1])
by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id ePZH8KfuohfS
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 18 Jan 2022 22:20:48 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.8.0
Received: from w1.tutanota.de (w1.tutanota.de [81.3.6.162])
by smtp2.osuosl.org (Postfix) with ESMTPS id E11F74010C
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 18 Jan 2022 22:20:47 +0000 (UTC)
Received: from w3.tutanota.de (unknown [192.168.1.164])
by w1.tutanota.de (Postfix) with ESMTP id DF9A3FA0305;
Tue, 18 Jan 2022 22:20:45 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1642544445;
s=s1; d=tutanota.de;
h=From:From:To:To:Subject:Subject:Content-Description:Content-ID:Content-Type:Content-Type:Content-Transfer-Encoding:Cc:Cc:Date:Date:In-Reply-To:MIME-Version:MIME-Version:Message-ID:Message-ID:Reply-To:References:Sender;
bh=evzJnOr0rp5kjuoMOLl0FItDMzpjtKWaH2hCXKLw+a0=;
b=NGOQOcAHJYyEuFbdIRpYzRIyuyxFsajpVy+5bgJFrwX9WCsPjRikRq0Mn5qQ/yQ1
c12svPd1ztTqsbLb6GS0+ywQcw33UqO+jaA+unZ4jHYZnO6w8Q8qafRa5nT89y7Ppxg
L/3MARNjNP7CYSPmUQBNAOA1VUKiyq0cwRl6psjTaLVvhFh/nnVkvbZZWNqVn1Pk6sZ
/6riu+aXR7sbfWRSlzvVZUmMWR4SDXgnhT+6bQjzgD5aqDz24DAD9u2XNKtqCb7NkuI
JYULdx07rgIbeJrosCTetoJJkLuzPPi8xzpZfpcEYDaM+uczaZ7Ld+D5gZT5pvFy0U+
zariN9FgXA==
Date: Tue, 18 Jan 2022 23:20:45 +0100 (CET)
From: Prayank <prayank@tutanota.de>
To: luke@dashjr.org
Message-ID: <MtjGn81--7-2@tutanota.de>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_Part_26838_1463751396.1642544445904"
X-Mailman-Approved-At: Tue, 18 Jan 2022 23:17:31 +0000
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] CTV BIP review
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: Tue, 18 Jan 2022 22:20:49 -0000
------=_Part_26838_1463751396.1642544445904
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Hi Luke,
This is the first competent review for CTV based on my understanding. I would not mention controversial things in this email but nobody cares about scammers and we will review everything irrespective of personal or legal attacks on developers because some people are prepared for it and capable, competent and healthy.
> nit: Poorly phrased. Even simple scripts can do that already.
Agree
> I would ideally like to see fully implemented BIPs for at least one of these (preferably the claimed CoinJoin improvements) before we move toward activation.
Agree
> Hard NACK on this. BIP 9 at this point represents developers attempting to disregard and impose their will over community consensus, as well as an attempt to force a miner veto backdoor/vulnerability on deployment. It should never be used again.
Agree
Other technical comments on BIP are appreciated however they would be better answered by Jeremy at this point or other as I am still researching and not confident to comment.
--
Prayank
A3B1 E430 2298 178F
------=_Part_26838_1463751396.1642544445904
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>Hi Luke,<br></div><div dir=3D"auto"><br></div><div dir=3D"auto">This i=
s the first competent review for CTV based on my understanding. I would not=
mention controversial things in this email but nobody cares about scammers=
and we will review everything irrespective of personal or legal attacks on=
developers because some people are prepared for it and capable, competent =
and healthy.<br></div><div dir=3D"auto"><br></div><div dir=3D"auto">> ni=
t: Poorly phrased. Even simple scripts can do that already.<br></div><div d=
ir=3D"auto"><br></div><div dir=3D"auto">Agree<br></div><div dir=3D"auto"><b=
r></div><div dir=3D"auto">> I would ideally like to see fully implemente=
d BIPs for at least one of these (preferably the claimed CoinJoin improveme=
nts) before we move toward activation.<br></div><div dir=3D"auto"><br></div=
><div dir=3D"auto">Agree<br></div><div dir=3D"auto"><br></div><div dir=3D"a=
uto">> Hard NACK on this. BIP 9 at this point represents developers atte=
mpting to disregard and impose their will over community consensus, as well=
as an attempt to force a miner veto backdoor/vulnerability on deployment. =
It should never be used again.<br></div><div dir=3D"auto"><br></div><div di=
r=3D"auto">Agree<br></div><div dir=3D"auto"><br></div><div dir=3D"auto">Oth=
er technical comments on BIP are appreciated however they would be better a=
nswered by Jeremy at this point or other as I am still researching and not =
confident to comment.<br></div><div dir=3D"auto"><br></div><div>-- <br></di=
v><div>Prayank<br></div><div><br></div><div dir=3D"auto">A3B1 E430 2298 178=
F<br></div> </body>
</html>
------=_Part_26838_1463751396.1642544445904--
|
