Bitcoin Signet support

With the halving a few blocks away, Bitcoin Testnet is not good (50sat/vB) at the moment and it’s been like this for a while. With Runes coming too, hopefully the dev activity will keep increasing, as we can see already on ICP. How long would it take to add Signet?

And can we have some new Bitcoin tags for topics? :smiley:

By the way, has anyone been experiencing issues with the Bitcoin Testnet canister? I’ve recently encountered the following problems: API being unavailable, state not syncing, and requests timing out, e.g.:

Yes, there are currently some issues with the BTC APIs, see InternetComputer Status - Bitcoin API Investigation, it’s being addressed, so hopefully things are back to normal soon.

1 Like

Thank you, @Manu. The incident is now marked as resolved, but I’m still getting the following error regarding canister g4xu7-jiaaa-aaaan-aaaaq-cai:

This issue happens when trying to use the Bitcoin API on testnet… How come?

1 Like

Yeah bitcoin testnet is very strange at the moment. Looking at now, it produced 100 blocks in the last 5 min, so more than 1000/hour, where bitcoin is supposed to do 6/hour. I would argue these are just bitcoin testnet problems. Under these conditions the bitcoin testnet canister will often be a bit behind and therefore return the error you’re seeing.

Yes, that brings us back to the need to add Bitcoin Signet as an option on ICP. What do you think, Manu? I also just opened this in this regard: ICP Developer Feedback

It’s something we briefly thought about some months ago but we didn’t look at it in great detail yet due to other priorities. I agree that this erratic behavior of BTC testnet makes the case for Signet more compelling, so it makes sense to at least assess if we could easily make this change.

1 Like

I had a similar problem.

1 Like

Same error I met last few days.

1 Like

Hi @_Eric, @cymqqqq,

It seems to be partially working right now! Can you double-check, too? I’m still occasionally getting the following error from some calls:

This error comes from the same canister you mentioned, @_Eric: Canister: g4xu7-jiaaa-aaaan-aaaaq-cai - ICP Dashboard (I’m not sure what it does, do you? It’s controlled by the NNS Root).

1 Like

Yes, I can use it as well. :smiley:

1 Like

Hello, I want to transfer ckTestBtc out now, but there is a limit. Do you have a good solution, or where can I get more TestBTC?

Hi @_Eric! I’m not sure if there’s a testnet ckBTC faucet (maybe @domwoe knows?). A possible solution that comes to mind is to run your own fork of the ckBTC minter and set up a lower value for retrieve_btc_min_amount.

I also agree that this limit is too high considering how badly testnet is working and that it is difficult to get a high amount of tBTC. Could you upgrade the ckBTC testnet canister to lower the retrieve_btc_min_amount, @Manu?

Regarding Signet, it is included in Bitcoin Core, so it should be pretty straightforward (and since it’s more centralized, it doesn’t have the same issues as Testnet). Here’s more info: Signet - Bitcoin Wiki

And this is the new topic on DX to add Signet support, please vote :pray::

Sounds reasonable to me, we’ll look into it!


Hey everyone, here’s an update regarding Testnet and why it won’t likely get better: Griefing Bitcoin's Testnet

Hi @Manu, how is it going? Would it be faster to add Testnet4? I’m getting a request timed out Error 255.

About the retrieve_btc_min_amount - can you please update it asap? It’s still 100000.

As you probably know, it is still unclear whether there will be an “official” Testnet4 or whether the current testnet will be upgraded. The latter case would be preferable in my opinion but I’m aware that there are opposing forces.

As Manu said, we are currently looking into adding support for Signet.