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
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
|
Return-Path: <alicexbt@protonmail.com>
Received: from smtp1.osuosl.org (smtp1.osuosl.org [140.211.166.138])
by lists.linuxfoundation.org (Postfix) with ESMTP id AA8B4C002D
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 2 Nov 2022 19:02:44 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp1.osuosl.org (Postfix) with ESMTP id 6F8E681E02
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 2 Nov 2022 19:02:44 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org 6F8E681E02
Authentication-Results: smtp1.osuosl.org;
dkim=pass (2048-bit key) header.d=protonmail.com header.i=@protonmail.com
header.a=rsa-sha256 header.s=protonmail3 header.b=c+1+EWQ5
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.602
X-Spam-Level:
X-Spam-Status: No, score=-1.602 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, FREEMAIL_FROM=0.001,
PDS_BTC_ID=0.499, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001]
autolearn=no autolearn_force=no
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 GHgC1MuxSYYO
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 2 Nov 2022 19:02:43 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org 61CE081DFB
Received: from mail-4318.protonmail.ch (mail-4318.protonmail.ch [185.70.43.18])
by smtp1.osuosl.org (Postfix) with ESMTPS id 61CE081DFB
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 2 Nov 2022 19:02:43 +0000 (UTC)
Date: Wed, 02 Nov 2022 19:02:33 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com;
s=protonmail3; t=1667415761; x=1667674961;
bh=UpWeRHiE248VS1q1Yg7Ob4iWMKnJUYQgwichoxLIMl8=;
h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References:
Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID:
Message-ID:BIMI-Selector;
b=c+1+EWQ5DUhQgu+QFxZ4Tsx8eadbGVp5gAebKeGZ8PWexAMmsKuEULyCOOk93Wx99
/KbuTd3QmQ95+syGQDY1mMBJiZeEv7V5+JoYAt5NCWDklkV+7k4bB4PzCHxqp/utwc
aFvCRhgUwUvTfUmKAbeXn3t+lfK53cUS2ExUsjgh8uGVtOLvPANVbZiuZ8Ok+mv4dR
t2afjbllSp5T5WRkejRlYBC8PO5CIP8h4miWCpn80tICUvI/+FzFpS4LMyoywyBy+B
DmKqIkkpVABxDUeQoY8+YluJDT2qvUTREyP2ZL2V5uYIuaNJYXUeQp/MGLDin1Irl5
UBZs6h4IvyO8A==
To: Peter Todd <pete@petertodd.org>
From: alicexbt <alicexbt@protonmail.com>
Message-ID: <fMZWicZXp5SM0ON8jgYuykBydOXcbgePbPfGKA0DQYtEDdiIr4bWljL_TqQHKtVKZRhvRXkEab47aaZw17OxGaSgOP2_w9_Owjb9WnTmsQ0=@protonmail.com>
In-Reply-To: <Y2I3w8O5X55sD/3C@petertodd.org>
References: <Y2I3w8O5X55sD/3C@petertodd.org>
Feedback-ID: 40602938:user:proton
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Wed, 02 Nov 2022 19:04:30 +0000
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Announcement: Full-RBF Miner Bounty
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, 02 Nov 2022 19:02:44 -0000
Hi Peter,
> tl;dr: I'm broadcasting full-RBF replacements paying extremely high fees =
to
> reward miners that turn on full-RBF. I'm starting small, just ~$100/block=
in
> times of congestion. Miner and pool profit margins are pretty small, on t=
he
> order of $1k/block in many cases, so I know it doesn't take that much mor=
e
> money to make a difference.
I appreciate this effort and perhaps this was all that was needed in additi=
on to Bitcoin Core's inclusion of full rbf support. Making it default right=
away or enabling preferential peering with service flag in a bitcoin core =
release was unnecessary.
> If you'd like to donate to this effort, send BTC to
> bc1qagmufdn6rf80kj3faw4d0pnhxyr47sevp3nj9m
Sorry, I don't trust you based on some of the things you support on Twitter=
. Hopefully, others will donate and help this bounty.
/dev/fd0
Sent with Proton Mail secure email.
------- Original Message -------
On Wednesday, November 2nd, 2022 at 2:56 PM, Peter Todd via bitcoin-dev <bi=
tcoin-dev@lists.linuxfoundation.org> wrote:
> I'm now running a full-RBf bounty program for miners.
>=20
> tl;dr: I'm broadcasting full-RBF replacements paying extremely high fees =
to
> reward miners that turn on full-RBF. I'm starting small, just ~$100/block=
in
> times of congestion. Miner and pool profit margins are pretty small, on t=
he
> order of $1k/block in many cases, so I know it doesn't take that much mor=
e
> money to make a difference.
>=20
> Why should you do this? Full-RBF/zeroconf has been discussed to death. Bu=
t
> tl;dr: You'll earn more money, and help transition Bitcoin to a more secu=
re
> mempool policy based on economic incentives rather than trust.
>=20
>=20
> If you're a miner and want to participate, the easiest way to so is to us=
e the
> mempoolfullrbf=3D1 option in the upcoming Bitcoin Core v24 release (eg th=
e
> 24.0rc3 tag), or use the mempoolreplacement=3Dfee option in Bitcoin Knots=
.
>=20
> You can also just modify the code yourself by removing the opt-in RBF che=
ck.
> For example against the v23.0 tag:
>=20
> $ git diff
> diff --git a/src/validation.cpp b/src/validation.cpp
> index 214112e2b..44c364623 100644
> --- a/src/validation.cpp
> +++ b/src/validation.cpp
> @@ -736,7 +736,7 @@ bool MemPoolAccept::PreChecks(ATMPArgs& args, Workspa=
ce& ws)
> // check all unconfirmed ancestors; otherwise an opt-in ancestor
> // might be replaced, causing removal of this descendant.
> if (!SignalsOptInRBF(*ptxConflicting)) {
> - return state.Invalid(TxValidationResult::TX_MEMPOOL_POLICY, "txn-mempoo=
l-conflict");
> + // return state.Invalid(TxValidationResult::TX_MEMPOOL_POLICY, "txn-mem=
pool-conflict");
> }
>=20
> ws.m_conflicts.insert(ptxConflicting->GetHash());
>=20
>=20
> Once you've enabled full-RBF, you need a full-RBF peer. I'm running a few=
of
> them:
>=20
> cup.nop.lol
> mug.nop.lol
> jar.nop.lol
> jug.nop.lol
>=20
> These nodes run a preferential peering patch (https://github.com/bitcoin/=
bitcoin/pull/25600)
> to ensure that full-RBF nodes are interconnected to each other and replac=
ements
> can easily propagate. Also feel free to contact me if you'd like to peer =
with a
> private node.
>=20
>=20
> If you'd like to donate to this effort, send BTC to
> bc1qagmufdn6rf80kj3faw4d0pnhxyr47sevp3nj9m
>=20
>=20
> ...and yes, I'm well aware that miners could collect this bounty in other=
ways,
> eg by raising minimum fees. Doing that also breaks zeroconf, so I'm not t=
oo
> concerned.
>=20
> --
> https://petertodd.org 'peter'[:-1]@petertodd.org
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
|
