Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE REQUEST] Support for testnet4 #666

Open
twofaktor opened this issue Sep 30, 2024 · 4 comments · May be fixed by #699
Open

[FEATURE REQUEST] Support for testnet4 #666

twofaktor opened this issue Sep 30, 2024 · 4 comments · May be fixed by #699

Comments

@twofaktor
Copy link

twofaktor commented Sep 30, 2024

Describe the new feature or enhancement

Considering that official support for testnet4 will likely be released with the imminent Bitcoin Core v28, this is a feature request to BTC RPC explorer as well.

Additional context

Bitcoin Core testnet4 support (included with v28): https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-28.0.md#testnet4bip94-support
Fulcrum support PR merged: cculianu/Fulcrum#255
Electrs support PR merged: romanz/electrs#1104 (edit)
LND coming support: lightningnetwork/lnd#8966
Electrumx support PR merged: spesmilo/electrumx#273

@schildbach
Copy link
Contributor

Bitcoin Core 28.0, including testnet4 support, has been released.

I think the current green "testnet color" icons can continue to be used for testnet4.

@schildbach
Copy link
Contributor

electrs 0.10.7, including testnet4 support, has been released.

@jmptbl
Copy link

jmptbl commented Nov 30, 2024

I'm trying to run btc-rpc-explorer with testnet4. I guess this explains the error I'm seeing?

image

@0xf0xx0
Copy link
Contributor

0xf0xx0 commented Dec 7, 2024

i'll spool up a testnet4 node and see what i can do.

@0xf0xx0 0xf0xx0 linked a pull request Dec 7, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants