-
Notifications
You must be signed in to change notification settings - Fork 105
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
Comments
Please prioritize this: nobody can test with Testnet3 anymore. Here's the link to claim the faucet for Testnet4. Claim Faucet for Testnet4 |
We should definitely consider it. |
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. |
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. |
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! |
@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: |
Multiple Bitcoin chain zetaclient config will be supported by #2870 |
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.
The text was updated successfully, but these errors were encountered: