diff options
| author | alicexbt <alicexbt@protonmail.com> | 2022-11-22 17:09:16 +0000 |
|---|---|---|
| committer | bitcoindev <bitcoindev@gnusha.org> | 2022-11-22 17:09:31 +0000 |
| commit | 76820c0abbff916d9ac4a71915213a4dc998db0e (patch) | |
| tree | 20bde304825043712386a970d4e33186b69e9644 | |
| parent | f8079b72fe12fc988ca40db4e0d8b3b6c6a358c4 (diff) | |
| download | pi-bitcoindev-76820c0abbff916d9ac4a71915213a4dc998db0e.tar.gz pi-bitcoindev-76820c0abbff916d9ac4a71915213a4dc998db0e.zip | |
Re: [bitcoin-dev] Custom signet for testing full RBF
| -rw-r--r-- | b2/832aec940643a415ca3a1449867278ad7d08fc | 224 |
1 files changed, 224 insertions, 0 deletions
diff --git a/b2/832aec940643a415ca3a1449867278ad7d08fc b/b2/832aec940643a415ca3a1449867278ad7d08fc new file mode 100644 index 000000000..0c1f4011f --- /dev/null +++ b/b2/832aec940643a415ca3a1449867278ad7d08fc @@ -0,0 +1,224 @@ +Return-Path: <alicexbt@protonmail.com> +Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133]) + by lists.linuxfoundation.org (Postfix) with ESMTP id C3127C002D + for <bitcoin-dev@lists.linuxfoundation.org>; + Tue, 22 Nov 2022 17:09:31 +0000 (UTC) +Received: from localhost (localhost [127.0.0.1]) + by smtp2.osuosl.org (Postfix) with ESMTP id 9123A408D7 + for <bitcoin-dev@lists.linuxfoundation.org>; + Tue, 22 Nov 2022 17:09:31 +0000 (UTC) +DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 9123A408D7 +Authentication-Results: smtp2.osuosl.org; + dkim=pass (2048-bit key) header.d=protonmail.com header.i=@protonmail.com + header.a=rsa-sha256 header.s=protonmail3 header.b=VNxl7KtN +X-Virus-Scanned: amavisd-new at osuosl.org +X-Spam-Flag: NO +X-Spam-Score: -2.101 +X-Spam-Level: +X-Spam-Status: No, score=-2.101 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, + SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] + autolearn=ham autolearn_force=no +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 Y7sWem5OaSQp + for <bitcoin-dev@lists.linuxfoundation.org>; + Tue, 22 Nov 2022 17:09:29 +0000 (UTC) +X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0 +DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 5ED6F400CB +Received: from mail-40137.protonmail.ch (mail-40137.protonmail.ch + [185.70.40.137]) + by smtp2.osuosl.org (Postfix) with ESMTPS id 5ED6F400CB + for <bitcoin-dev@lists.linuxfoundation.org>; + Tue, 22 Nov 2022 17:09:28 +0000 (UTC) +Date: Tue, 22 Nov 2022 17:09:16 +0000 +DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; + s=protonmail3; t=1669136964; x=1669396164; + bh=q+NPZjJD/5FJf5Zy1azzOhhsKSlD1yiNnQw/w+v8QP0=; + 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=VNxl7KtN0o/ZaqRn0NN1JzsApVXbdR015d4nRfuutUmjUxv7mfNnJfsdYd9ISCxLx + rMBqcDn7MIPACpFNJU5J9diq5jQUA63Ku0BcgE0jP3wjaA9FkF2YfSHRPhLjg3SiQp + 9PfjD0l4RsOU/lT1IrNxF1PjZsw0qP8Cvte6BTeSWcJcBcgu+VDeEghjPt6xwpQKl4 + S2WTADAS+NZHUGw+04C0qd4uLupGQIMp3QTU11IB0A93HO3Id/gnBGYz/61BpLUdOA + KPZ1CqAbzXmaVoVPKWvUG8RVMHNJNROrGAfs1SorSU+JL/hJKi5uxsxGUEtfhN2okb + HhwTXEWQ5Ei2Q== +To: Michael Folkson <michaelfolkson@protonmail.com> +From: alicexbt <alicexbt@protonmail.com> +Message-ID: <3EotthoDUEkl3Vqv_PWkF47ytiPvGjBfNcK9fgWDEWkOYMgwdst38aoW7QJldTdIUKCPKV9fcsUnrdjs5aze6vRgs_TAU_qn3EoTU7DyAZc=@protonmail.com> +In-Reply-To: <_rvhg7VmWlwMShoKBmFOiEsVoI7so01bHe6_WI11o3bWmpllNhiqHBZQ7O_4GFu-OTqLaq8p4ndom2WeovfV59wnUbtqjAVnNckraYGU8AA=@protonmail.com> +References: <6lyH4IyNtVBlm_9wsr5UEAi8stIZN8OKNrcSJMOTJUiKE4MLoAMXluIR-4XJBHSwxpffEEsDCwkjQsrApqssvbIX_z_prQqfYbVa7JRJ3vE=@protonmail.com> + <_rvhg7VmWlwMShoKBmFOiEsVoI7so01bHe6_WI11o3bWmpllNhiqHBZQ7O_4GFu-OTqLaq8p4ndom2WeovfV59wnUbtqjAVnNckraYGU8AA=@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: Tue, 22 Nov 2022 17:23:14 +0000 +Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org> +Subject: Re: [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: Tue, 22 Nov 2022 17:09:31 -0000 + +Hi Michael, + +> In this particular case the -mempoolfullrbf configuration option is in th= +e recent Bitcoin Core 24.0 release and so can be used both on mainnet and t= +he default signet, testnet etc. What could be tested on this custom signet = +that can't be tested on the default signet with Bitcoin Core 24.0? Perhaps = +there are some things that are easier to test with a smaller custom signet = +network starting from scratch? + +1. Signet miners and dictators are not interested to use full RBF +2. Testnet is weird and I only use it when a project doesn't support signet +3. Mainnet v24.0 is not released yet although Peter Todd is trying few thin= +gs, I am not even sure if it will be available, testing should not depend o= +n politics. +4. Main/Default Signet miners and dictators did not respond or agree to use= + full RBF. + +Testing is important and I love it. I do not care about others. + +> I know a number of people have struggled (e.g. [0], [1]) to get a custom = +signet set up. I think the CTV signet took a while to get set up too. It se= +ems you followed the instructions on the Bitcoin wiki [2] for setting this = +one up? Was there anything you found difficult or was counterintuitive gett= +ing this custom signet set up? You are the sole block signer on this custom= + signet. How regularly are you mining blocks (e.g. strictly every 10 minute= +s, replicating the Poisson process on mainnet, adhoc etc?) Are you running = +this custom signet node on the same machine as a default signet, mainnet, t= +estnet full node? I'm a little tentative to start joining custom signet net= +works on the same machine that is already running other nodes but perhaps t= +here are no problems.=20 + +I had no issues except this command: + +`` +$ ../contrib/signet/miner --cli=3D"./bitcoin-cli" calibrate --grind-cmd=3D"= +./bitcoin-util grind" --seconds=3D600 +``` + +I had no clue we need to wait for some seconds/minutes for output. Although= + its okay. + +I used default settings and it should mine with it forever or my AWS subscr= +iption is cancelled.=20 + +I am trying to help Bitcoin. Although not a big influencer. If most of the = +developers think its okay to test it directly on mainnet, there is nothing = +wrong with it. You will get some insights/bugs from this experiment if enou= +gh users try it. + + +Sent with Proton Mail secure email.ichael + +/dev/fd0 + +------- Original Message ------- +On Tuesday, November 22nd, 2022 at 4:50 PM, Michael Folkson <michaelfolkson= +@protonmail.com> wrote: + + +> Hi alicexbt +>=20 +> Thanks for setting this up. Generally it seems to me like an excellent id= +ea to set up custom signets (and/or get proposals enabled on the default si= +gnet) for testing and experimenting with new proposals. +>=20 +> I have two questions. +>=20 +> 1) In this particular case the -mempoolfullrbf configuration option is in= + the recent Bitcoin Core 24.0 release and so can be used both on mainnet an= +d the default signet, testnet etc. What could be tested on this custom sign= +et that can't be tested on the default signet with Bitcoin Core 24.0? Perha= +ps there are some things that are easier to test with a smaller custom sign= +et network starting from scratch? +>=20 +> 2) I know a number of people have struggled (e.g. 0, 1) to get a custom s= +ignet set up. I think the CTV signet took a while to get set up too. It see= +ms you followed the instructions on the Bitcoin wiki 2 for setting this one= + up? Was there anything you found difficult or was counterintuitive getting= + this custom signet set up? You are the sole block signer on this custom si= +gnet. How regularly are you mining blocks (e.g. strictly every 10 minutes, = +replicating the Poisson process on mainnet, adhoc etc?) Are you running thi= +s custom signet node on the same machine as a default signet, mainnet, test= +net full node? I'm a little tentative to start joining custom signet networ= +ks on the same machine that is already running other nodes but perhaps ther= +e are no problems. +>=20 +> I'm not sure yet if I have a use case in mind for this particular custom = +signet but I'm very interested in custom signet setup generally and the doc= +s/resources to make this as easy as possible so thanks again for posting ab= +out this. +>=20 +> Thanks +> Michael +>=20 +> 0: https://bitcoin.stackexchange.com/questions/114477/could-someone-share= +-with-me-some-documentations-or-sites-on-how-to-set-up-a-cust +> 1: https://bitcoin.stackexchange.com/questions/114724/peer-discovery-on-a= +-custom-signet-custom-signetchallenge +> 2: 0: https://en.bitcoin.it/wiki/Signet#Custom_Signet +>=20 +> -- +> Michael Folkson +> Email: michaelfolkson at protonmail.com +> Keybase: michaelfolkson +> PGP: 43ED C999 9F85 1D40 EAF4 9835 92D6 0159 214C FEE3 +>=20 +>=20 +> ------- Original Message ------- +> On Sunday, November 20th, 2022 at 08:36, alicexbt via bitcoin-dev bitcoin= +-dev@lists.linuxfoundation.org wrote: +>=20 +>=20 +>=20 +> > Hi Bitcoin Developers, +> >=20 +> > I have setup a custom signet for testing full RBF. You can connect to o= +ne or more of these nodes using `addnode`: +> >=20 +> > 13.115.34.55 (issuer, full-rbf) +> > kfupbqwb2yvzzqjomfq5pkem553a6uzp2k73seqn4d46smy7azua.b32.i2p (rbf-optin= +) +> > luvczzzppiqnc2b7poivkxlugafe3uqaj245ebjqxtceio7poaorqcyd.onion (full-rb= +f) +> >=20 +> > Example config: +> >=20 +> > `signet=3D1 signetchallenge=3D5121035daaa313aada6310340a242af17238cc1fd= +8849e875940bce65a60ac7e0e0ff751ae proxy=3D127.0.0.1:9050 [signet] addnode= +=3Dluvczzzppiqnc2b7poivkxlugafe3uqaj245ebjqxtceio7poaorqcyd.onion mempoolfu= +llrbf=3D1` +> >=20 +> > Example for a simple test case: +> >=20 +> > - 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 `memp= +oolfullrbf=3D1` in config and compile bitcoind using PR #26454 branch +> > - Broadcast Tx1 using node 2 and replace with Tx2 using `bumpfee` RPC +> >=20 +> > It will be fun to test with more nodes joining this custom signet. If a= +nyone interested to test, please post your bitcoin address in full-rbf room= +. We can even setup an explorer if this experiment makes sense. +> >=20 +> > Sent with Proton Mail secure email. +> >=20 +> > /dev/fd0 +> > _______________________________________________ +> > bitcoin-dev mailing list +> > bitcoin-dev@lists.linuxfoundation.org +> > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev + |