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
|
Return-Path: <prayank@tutanota.de>
Received: from smtp4.osuosl.org (smtp4.osuosl.org [140.211.166.137])
by lists.linuxfoundation.org (Postfix) with ESMTP id F0007C000B
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 18 Feb 2022 02:08:05 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp4.osuosl.org (Postfix) with ESMTP id DE4B540891
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 18 Feb 2022 02:08:05 +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: smtp4.osuosl.org (amavisd-new);
dkim=pass (2048-bit key) header.d=tutanota.de
Received: from smtp4.osuosl.org ([127.0.0.1])
by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id cTUPzcGKMBjk
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 18 Feb 2022 02:08:05 +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 smtp4.osuosl.org (Postfix) with ESMTPS id EED67408E3
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 18 Feb 2022 02:08:04 +0000 (UTC)
Received: from w3.tutanota.de (unknown [192.168.1.164])
by w1.tutanota.de (Postfix) with ESMTP id 589F4FBF85F;
Fri, 18 Feb 2022 02:08:02 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1645150082;
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=P2p6hYdMaPlRPX0J1Gw7RiOdW6itXwCkezRmZMEpjJk=;
b=Z9mvrv9c4ik6M48HfPy1j53U1uU2ud/innxuog8THIMC1qardniJAcKWslQIjEOX
u96vV1WxtMsgkWSYNp7jSWAYOdTi/Yu90s0dCrNr0H10fLbojO03gepnsOrZZEe7Zb6
A8IThr7b69fMkwAWxMgdnGMfMOBNY1CR+CvDyNhvXNsNm0sYif1Nv/Hr5rfS6AeT4Dr
+RNzmq9zM+4yJqrwK6RHeTWVG1N8gO0Pd8aGrKfMpjOoj1hwIzA0HvaCm+/BDlQhtN6
aoTXURFySUchPrc2vUoOM0h4wDX3IUSfgsVQEjmuBDK2wgiGOxuv5eJ6nKEfk1Asu+4
mFt8QJ02VQ==
Date: Fri, 18 Feb 2022 03:08:02 +0100 (CET)
From: Prayank <prayank@tutanota.de>
To: James Obeirne <james.obeirne@gmail.com>
Message-ID: <Mw9_W3f--3-2@tutanota.de>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_Part_109811_2051551271.1645150082351"
X-Mailman-Approved-At: Fri, 18 Feb 2022 08:45:43 +0000
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Thoughts on fee bumping
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: Fri, 18 Feb 2022 02:08:06 -0000
------=_Part_109811_2051551271.1645150082351
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
> If anyone has any indication that there are miners running forks of bitco=
ind that change this behavior, I'd be curious to know it.
It is possible because some mining pools use bitcoind with custom patches.=
=C2=A0
Example: https://twitter.com/0xB10C/status/1461392912600776707 (f2pool)
--=20
Prayank
A3B1 E430 2298 178F
------=_Part_109811_2051551271.1645150082351
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div>> If anyone has any indication that there are miners running forks of bitcoind that change this behavior, I'd be curious to know it.</div><div dir="auto"><br></div><div dir="auto">It is possible because some mining pools use bitcoind with custom patches. <br></div><div dir="auto"><br></div><div dir="auto">Example: https://twitter.com/0xB10C/status/1461392912600776707 (f2pool)</div><div><br></div><div dir="auto"><br></div><div>-- <br></div><div>Prayank<br></div><div><br></div><div dir="auto">A3B1 E430 2298 178F<br></div> </body>
</html>
------=_Part_109811_2051551271.1645150082351--
|
