summaryrefslogtreecommitdiff
path: root/19/2c1902adcc3ba477b9e0588b0ce6f6012640c4
blob: 45eab2c5ae19dbafd940bb46ffc32d3bcc8ff616 (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
Return-Path: <alicexbt@protonmail.com>
Received: from smtp3.osuosl.org (smtp3.osuosl.org [IPv6:2605:bc80:3010::136])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 0E0A9C002D
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun, 20 Nov 2022 06:36:33 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp3.osuosl.org (Postfix) with ESMTP id E385C60AC4
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun, 20 Nov 2022 06:36:32 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org E385C60AC4
Authentication-Results: smtp3.osuosl.org;
 dkim=pass (2048-bit key) header.d=protonmail.com header.i=@protonmail.com
 header.a=rsa-sha256 header.s=protonmail3 header.b=q1Kg6XCz
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, FREEMAIL_FROM=0.001,
 RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001]
 autolearn=ham autolearn_force=no
Received: from smtp3.osuosl.org ([127.0.0.1])
 by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id K-RqRx1oLmNX
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun, 20 Nov 2022 06:36:31 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org E091E60A82
Received: from mail-4324.protonmail.ch (mail-4324.protonmail.ch [185.70.43.24])
 by smtp3.osuosl.org (Postfix) with ESMTPS id E091E60A82
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun, 20 Nov 2022 06:36:30 +0000 (UTC)
Date: Sun, 20 Nov 2022 06:36:23 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com;
 s=protonmail3; t=1668926188; x=1669185388;
 bh=+WBRYkH8JbHOZNHtJ5m/KmUBvSGi8WIJo2NkrTDDmCc=;
 h=Date:To:From:Subject:Message-ID:Feedback-ID:From:To:Cc:Date:
 Subject:Reply-To:Feedback-ID:Message-ID:BIMI-Selector;
 b=q1Kg6XCz/Sdo+3LsfyfaCUEnhn7KL/JQyCtjeqdbiwTsRmtg4nbXjemNVRacWQxlz
 DmuF+/kkAMks7ctfwnODyO1y3DUl1agvJQjJcHASerQ0DsXxQA7BKx1Uq2TkGi8q6G
 kIJ7vja+bntZYvASkXCtS+3i1V9cTZOR8adYlDEPPDqJmogCNnK1q26wPx91HdkPT4
 rF/5YQgLLzbJd70iGHKFnN/M8lzF+nkL/B52kUHgTw7mbEedO2ARv2TwLg2Z3X1FsI
 uAO0UE/hGnGAm6xJDnhLtOpgnH6QTIzp8/uQRTn0MdKUPddVKZ+qPHCNu++x//D2Nx
 o3gEYveDAcsaw==
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
From: alicexbt <alicexbt@protonmail.com>
Message-ID: <6lyH4IyNtVBlm_9wsr5UEAi8stIZN8OKNrcSJMOTJUiKE4MLoAMXluIR-4XJBHSwxpffEEsDCwkjQsrApqssvbIX_z_prQqfYbVa7JRJ3vE=@protonmail.com>
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: Sun, 20 Nov 2022 14:15:46 +0000
Subject: [bitcoin-dev] Custom signet for testing full RBF
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, 20 Nov 2022 06:36:33 -0000

Hi Bitcoin Developers,

I have setup a [custom signet][0] for testing full RBF. You can connect to =
one or more of these nodes using `addnode`:

13.115.34.55 (issuer, full-rbf)
kfupbqwb2yvzzqjomfq5pkem553a6uzp2k73seqn4d46smy7azua.b32.i2p (rbf-optin)
luvczzzppiqnc2b7poivkxlugafe3uqaj245ebjqxtceio7poaorqcyd.onion (full-rbf)

Example config:

```
signet=3D1
signetchallenge=3D5121035daaa313aada6310340a242af17238cc1fd8849e875940bce65=
a60ac7e0e0ff751ae
proxy=3D127.0.0.1:9050

[signet]
addnode=3Dluvczzzppiqnc2b7poivkxlugafe3uqaj245ebjqxtceio7poaorqcyd.onion

mempoolfullrbf=3D1
```

Example for a simple test case:

- Run 2 nodes
- Connect node 1 with i2p node and use default opt-in rbf
- Connect node 2 with node 1 and onion node. This node should use `mempoolf=
ullrbf=3D1` in config and compile bitcoind using PR [#26454][1] branch
- Broadcast Tx1 using node 2 and replace with Tx2 using `bumpfee` RPC

It will be fun to test with more nodes joining this custom signet. If anyon=
e interested to test, please post your bitcoin address in [full-rbf room][2=
]. We can even setup an explorer if this experiment makes sense.

[0]: https://en.bitcoin.it/wiki/Signet#Custom_Signet
[1]: https://github.com/bitcoin/bitcoin/pull/26454
[2]: #full-rbf:matrix.org

Sent with Proton Mail secure email.

/dev/fd0