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

plan to integrate testnet4 #3750

Closed
ordinariusprof opened this issue May 13, 2024 · 10 comments
Closed

plan to integrate testnet4 #3750

ordinariusprof opened this issue May 13, 2024 · 10 comments

Comments

@ordinariusprof
Copy link
Contributor

since testnet3 is unusable, is there a plan to utilize testnet4 as discussed here: bitcoin/bitcoin#29775 ?

@cryptoni9n
Copy link
Collaborator

as an aside to this, I saw today that the latest version of Sparrow (v1.9.1) has integrated testnet4 https://x.com/SparrowWallet/status/1790312602918126026

@raphjaph
Copy link
Collaborator

We'll definitely run it as soon as it is in a release version of Bitcoin Core

@Vardominator
Copy link

@raphjaph Do you have plans for releasing support for testnet4? Bitcoin Core 28.0 was released recently.

@raphjaph
Copy link
Collaborator

As soon as I merge #3962 ord will be compatible with v28

@cryptoquick
Copy link
Contributor

cryptoquick commented Oct 23, 2024

@raphjaph I just tried running ord on testnet4 but bitcoind uses port 48332 by default. Setting that to 18332 results in this error:

Oct 23 01:43:12 testnet4-deployment sh[30535]: error: Failed to connect to Bitcoin Core RPC at `127.0.0.1:18332/`:  JSON error: invalid value: string "testnet4", expected bitcoin network encoded as a string

Might be an issue you'll need to reopen this for. Build hash was: ef2212b

@raphjaph
Copy link
Collaborator

You'll have to change some parsing logic in the code, we look for testnet3 in places instead of testnet4. We're not going to officially support testnet4 until next year because we only want to support one testnet

@donnlee
Copy link

donnlee commented Dec 16, 2024

testnet3 transactions fee are >4000 sats/vB, making it unusable because there are no faucets that give enough sats.
I've moved to testnet4, but now I need ord or unisat.io or ordinals.com to support testnet4.
I tried search-n-replace of testnet3 to testnet4 but the error persists.

Does anyone have a fork of ord that supports testnet4 today?

@raphjaph
Copy link
Collaborator

raphjaph commented Dec 17, 2024

you could also try signet. If you drop me a signet address I'll send you some sats

@donnlee
Copy link

donnlee commented Dec 17, 2024

Oh awesome idea. Thank you!
And it seems ordinals.com supports signet, https://signet.ordinals.com

@raphjaph
Copy link
Collaborator

#4135

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants