From: alicexbt <alicexbt@protonmail•com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] Custom signet for testing full RBF
Date: Sun, 20 Nov 2022 06:36:23 +0000 [thread overview]
Message-ID: <6lyH4IyNtVBlm_9wsr5UEAi8stIZN8OKNrcSJMOTJUiKE4MLoAMXluIR-4XJBHSwxpffEEsDCwkjQsrApqssvbIX_z_prQqfYbVa7JRJ3vE=@protonmail.com> (raw)
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=1
signetchallenge=5121035daaa313aada6310340a242af17238cc1fd8849e875940bce65a60ac7e0e0ff751ae
proxy=127.0.0.1:9050
[signet]
addnode=luvczzzppiqnc2b7poivkxlugafe3uqaj245ebjqxtceio7poaorqcyd.onion
mempoolfullrbf=1
```
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 `mempoolfullrbf=1` 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 anyone 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
next reply other threads:[~2022-11-20 6:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-20 6:36 alicexbt [this message]
2022-11-22 11:20 ` Michael Folkson
2022-11-22 17:09 ` alicexbt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='6lyH4IyNtVBlm_9wsr5UEAi8stIZN8OKNrcSJMOTJUiKE4MLoAMXluIR-4XJBHSwxpffEEsDCwkjQsrApqssvbIX_z_prQqfYbVa7JRJ3vE=@protonmail.com' \
--to=alicexbt@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox