Return-Path: Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133]) by lists.linuxfoundation.org (Postfix) with ESMTP id A06F9C002D for ; Tue, 22 Nov 2022 11:20:58 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp2.osuosl.org (Postfix) with ESMTP id 854D640332 for ; Tue, 22 Nov 2022 11:20:58 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 854D640332 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=NvT1OLiq 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 smtp2.osuosl.org ([127.0.0.1]) by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r0psriGuy3GW for ; Tue, 22 Nov 2022 11:20:57 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org EBF5A4029F Received: from mail-4322.protonmail.ch (mail-4322.protonmail.ch [185.70.43.22]) by smtp2.osuosl.org (Postfix) with ESMTPS id EBF5A4029F for ; Tue, 22 Nov 2022 11:20:56 +0000 (UTC) Date: Tue, 22 Nov 2022 11:20:44 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1669116054; x=1669375254; bh=Qbabo79JGYnXW5rJNMGBDLDfDSNtDTbbSzhOgahr1iU=; h=Date:To:From:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=NvT1OLiqlEMU1GEYoNFgedvdHd4v5utKMpKZMYqJ3Ib3Ca3pGjzPb+t6ariGTwxic 3vQ6hcwf1MQBeMfZ4BAY7RTH2ScNZcvnOgO9dh7DE5yMbkH6yTXdgXF/eDm0Uk7/84 KgMyp6U9moUwwQNFodboGjoJfpAYaQrCQ3qna8fWF9WSeyOW6rCR1cCPXyzX0XxICU jXvVpbVw+O9Q+Jvrnk2vlu/3qRPO+/iZyVxP+DDwx9yFfdB7F0rx73gXeldlLjBLen hnRBtwBa4y66Xjy4rXuhtKi+2jCCwfIOkxxn2sWoDoLg6OWMSyOhJ3o/g6/bErTKyn srZmHeEq5kmCw== To: alicexbt , Bitcoin Protocol Discussion From: Michael Folkson Message-ID: <_rvhg7VmWlwMShoKBmFOiEsVoI7so01bHe6_WI11o3bWmpllNhiqHBZQ7O_4GFu-OTqLaq8p4ndom2WeovfV59wnUbtqjAVnNckraYGU8AA=@protonmail.com> In-Reply-To: <6lyH4IyNtVBlm_9wsr5UEAi8stIZN8OKNrcSJMOTJUiKE4MLoAMXluIR-4XJBHSwxpffEEsDCwkjQsrApqssvbIX_z_prQqfYbVa7JRJ3vE=@protonmail.com> References: <6lyH4IyNtVBlm_9wsr5UEAi8stIZN8OKNrcSJMOTJUiKE4MLoAMXluIR-4XJBHSwxpffEEsDCwkjQsrApqssvbIX_z_prQqfYbVa7JRJ3vE=@protonmail.com> Feedback-ID: 27732268: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 11:38:41 +0000 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Nov 2022 11:20:58 -0000 Hi alicexbt Thanks for setting this up. Generally it seems to me like an excellent idea= to set up custom signets (and/or get proposals enabled on the default sign= et) for testing and experimenting with new proposals. I have two questions. 1) In this particular case the -mempoolfullrbf configuration option is in t= he recent Bitcoin Core 24.0 release and so can be used both on mainnet and = the 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? 2) 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 s= eems you followed the instructions on the Bitcoin wiki [2] for setting this= one up? Was there anything you found difficult or was counterintuitive get= ting this custom signet set up? You are the sole block signer on this custo= m signet. How regularly are you mining blocks (e.g. strictly every 10 minut= es, replicating the Poisson process on mainnet, adhoc etc?) Are you running= this custom signet node on the same machine as a default signet, mainnet, = testnet full node? I'm a little tentative to start joining custom signet ne= tworks on the same machine that is already running other nodes but perhaps = there are no problems.=20 I'm not sure yet if I have a use case in mind for this particular custom si= gnet but I'm very interested in custom signet setup generally and the docs/= resources to make this as easy as possible so thanks again for posting abou= t this. Thanks Michael [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 -- Michael Folkson Email: michaelfolkson at protonmail.com Keybase: michaelfolkson PGP: 43ED C999 9F85 1D40 EAF4 9835 92D6 0159 214C FEE3 ------- Original Message ------- On Sunday, November 20th, 2022 at 08:36, alicexbt via bitcoin-dev wrote: > Hi Bitcoin Developers, >=20 > I have setup a [custom signet][0] for testing full RBF. You can connect t= o one or more of these nodes using `addnode`: >=20 > 13.115.34.55 (issuer, full-rbf) > kfupbqwb2yvzzqjomfq5pkem553a6uzp2k73seqn4d46smy7azua.b32.i2p (rbf-optin) > luvczzzppiqnc2b7poivkxlugafe3uqaj245ebjqxtceio7poaorqcyd.onion (full-rbf) >=20 > Example config: >=20 > `signet=3D1 signetchallenge=3D5121035daaa313aada6310340a242af17238cc1fd88= 49e875940bce65a60ac7e0e0ff751ae proxy=3D127.0.0.1:9050 [signet] addnode=3Dl= uvczzzppiqnc2b7poivkxlugafe3uqaj245ebjqxtceio7poaorqcyd.onion mempoolfullrb= f=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 `mempoo= lfullrbf=3D1` in config and compile bitcoind using PR [#26454][1] 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 any= one interested to test, please post your bitcoin address in [full-rbf room]= [2]. We can even setup an explorer if this experiment makes sense. >=20 > [0]: https://en.bitcoin.it/wiki/Signet#Custom_Signet > [1]: https://github.com/bitcoin/bitcoin/pull/26454 > [2]: #full-rbf:matrix.org >=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