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

Migrate supported Bitcoin testnet network to Testnet4 or Signet #2242

Open
lumtis opened this issue May 22, 2024 · 9 comments
Open

Migrate supported Bitcoin testnet network to Testnet4 or Signet #2242

lumtis opened this issue May 22, 2024 · 9 comments
Assignees
Labels
operation Operation related (no codebase change involved)

Comments

@lumtis
Copy link
Member

lumtis commented May 22, 2024

Describe the Issue

Bitcoin testnet3 might become deprecated and is not optimal for Bitcoin testing (chain much faster than mainnet)

This task is about finding alternative to Bitcoin testnet3 for testnet

We might want to move to Testnet4: https://mempool.space/testnet4

Blocked by #2728

We'll be adding Signet support as 1st step to provide a stable test network.

@lumtis lumtis added this to the v17 milestone May 23, 2024
@ronaldoguedess
Copy link

Please prioritize this: nobody can test with Testnet3 anymore. Here's the link to claim the faucet for Testnet4.

Claim Faucet for Testnet4
https://coinfaucet.eu/en/btc-testnet4/

@lumtis lumtis modified the milestones: v19, v18 Jun 21, 2024
@lumtis
Copy link
Member Author

lumtis commented Jun 26, 2024

We should definitely consider it.
It doesn't seem though btcd has completed support for testnet4: btcsuite/btcd#2187
We might need to consider forking btcd

@fadeev
Copy link
Member

fadeev commented Jun 26, 2024

@ronaldoguedess #2386

@ronaldoguedess
Copy link

We should definitely consider it. It doesn't seem though btcd has completed support for testnet4: btcsuite/btcd#2187 We might need to consider forking btcd

Testnet4 might not be finalized yet, but it's performing 1000% better than Testnet3, which is now deprecated. This makes it the perfect time to add support for Testnet4.

@jcvernaleo
Copy link

Just so you know, someone is actively working on adding the current testnet4 to btcd now (not just that open issue that we haven't finished).

Hope to have it in within a few days.

@jcvernaleo
Copy link

I'd of course encourage contributing to btcd rather than forking. If you tag me in any PRs, I'll make sure to take a look at it sooner rather than later!

@lumtis lumtis modified the milestones: July, August Jul 18, 2024
@lumtis lumtis modified the milestones: August, Future Jul 31, 2024
@CharlieMc0 CharlieMc0 added the operation Operation related (no codebase change involved) label Aug 26, 2024
@lumtis lumtis changed the title Explore new alternative for Bitcoin testnet3 Migrate supported Bitcoin testnet network to Testnet4 Aug 26, 2024
@lumtis lumtis changed the title Migrate supported Bitcoin testnet network to Testnet4 Migrate supported Bitcoin testnet network to Testnet4 or Signet Aug 28, 2024
@lumtis
Copy link
Member Author

lumtis commented Aug 28, 2024

@ronaldoguedess we're look into migrating Bitcoin testnet in one of the coming release

Do you have an opinion about using Signet instead of Testnet4?

@ronaldoguedess
Copy link

@ronaldoguedess we're look into migrating Bitcoin testnet in one of the coming release

Do you have an opinion about using Signet instead of Testnet4?

I knew signet a few days ago on the mempool, but I believe Testnet4 will require fewer changes and it's newer.

Testnet4 also offers some great faucet tools:

Mempool Testnet4 Faucet
CoinFaucet Testnet4

@lumtis lumtis removed this from the Future milestone Sep 16, 2024
@ws4charlie
Copy link
Contributor

Multiple Bitcoin chain zetaclient config will be supported by #2870

@lumtis lumtis added this to the October Release (v22) milestone Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
operation Operation related (no codebase change involved)
Projects
None yet
Development

No branches or pull requests

6 participants