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
|
Return-Path: <sl.lmysyibug4zdqnbwga4syibsgm4tgobtlu.lxwfrv42th3fo@dralias.com>
Received: from smtp1.osuosl.org (smtp1.osuosl.org [IPv6:2605:bc80:3010::138])
by lists.linuxfoundation.org (Postfix) with ESMTP id 07F1AC002D
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 16 Jun 2022 05:51:01 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp1.osuosl.org (Postfix) with ESMTP id D7CE783155
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 16 Jun 2022 05:51:00 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -2.102
X-Spam-Level:
X-Spam-Status: No, score=-2.102 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, SPF_HELO_PASS=-0.001,
SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: smtp1.osuosl.org (amavisd-new);
dkim=pass (1024-bit key) header.d=dralias.com
Received: from smtp1.osuosl.org ([127.0.0.1])
by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id sMo3gLBNyh70
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 16 Jun 2022 05:51:00 +0000 (UTC)
X-Greylist: delayed 00:07:12 by SQLgrey-1.8.0
Received: from mail-200164.simplelogin.co (mail-200164.simplelogin.co
[176.119.200.164])
by smtp1.osuosl.org (Postfix) with ESMTPS id 25447830E6
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 16 Jun 2022 05:50:59 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dralias.com; s=dkim;
t=1655358226;
h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
to:to:cc:mime-version:mime-version:content-type:content-type:
content-transfer-encoding:content-transfer-encoding:
in-reply-to:in-reply-to:references:references;
bh=9kpxNX6yf8MBVQEyzwRYqyqe8yzaCuGrbaY/erZbZFM=;
b=FSc9Z308/3QKrSQjAfCCzXfkkiT44eyTHRGIbVaIPhfGhK1X8Iu7DJIYUTaHeX19yCHU2i
Ifbap2/uawsaMZX0i2/rGsj7uNquyUWbLKdUs/g1XQKTotO9/5f2VeWYgyp9oKn2/fZoDj
J8YLi+IKurBBrz/AoNGBZOEqTnQY0BQ=
MIME-Version: 1.0
In-Reply-To: <dYLEcCTOYwMe7umkzbxdFz-sp5ZwqHU6DcpAg8M8p-ANg8QWSafISIzDXhbGiAHlV6eInfar2ll9oWviwox4SZ7QwfgqXkIbgq_fvcaUz0M=@protonmail.com>
Date: Thu, 16 Jun 2022 07:43:33 +0200
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
From: linuxfoundation.cndm1@dralias.com
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Message-ID: <165535822613.7.2651335771202625212.47284609@dralias.com>
References: <CALZpt+GOh-7weEypT9JrzcwthZJqHOfj7sf9FMuqi5_FZv0g7w@mail.gmail.com>
<7aP7ve-x6uMLSY2a9ZvpkyEc7uOdWmCGOs-S2ly1klRKzm5kVT4zjC9i0V6k1R0Cr9Xloq6Z4zmZ0LfquOxFtyhrA0RgsfG4qq760T4dfZM=@protonmail.com>
<CAB3F3DuhMQn_fSiXqqzrUMhDm7D=AiKg4nSO71372WzJFCr9EQ@mail.gmail.com>
<dYLEcCTOYwMe7umkzbxdFz-sp5ZwqHU6DcpAg8M8p-ANg8QWSafISIzDXhbGiAHlV6eInfar2ll9oWviwox4SZ7QwfgqXkIbgq_fvcaUz0M=@protonmail.com>
X-SimpleLogin-Type: Reply
X-SimpleLogin-EmailLog-ID: 47284609
X-SimpleLogin-Want-Signing: yes
X-Mailman-Approved-At: Thu, 16 Jun 2022 08:01:47 +0000
Subject: Re: [bitcoin-dev] Playing with full-rbf peers for fun and L2s
security
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: Thu, 16 Jun 2022 05:51:01 -0000
alicexbt wrote:
> I do not have issues with multiple RBF policies being tried out and full-=
rbf being one of them. My disagreements are with rationale, lack of basic o=
ptions in Bitcoin Core to employ/disable different RBF policies and a few a=
rguments made in support for full-rbf. Whether it appears strawman or offto=
pic on github, there should be a place to share these disagreements.
Bitcoin Core is open source software, where developers open pull
requests to try to get them merged after review. If you see a "lack of
basic options" and no one has opened a pull request for it, it may be
for two reasons. First, it could be that it just doesn't make sense,
so no one sees a point in implementing it. Secondly, it may be that it
isn't on anyone's list of priorities. In the second case, you are
welcome to share your preference once. Moreover, no one is holding you
back to implement it yourself and suggest a pull request. However,
repeatedly demanding others to do it for you is not helpful in open
source software development.
cndm1
|
