I got an error calling update_balance:“management call ‘bitcoin_get_utxos’ failed: canister error: IC0503: Canister g4xu7-jiaaa-aaaan-aaaaq-cai trapped explicitly: Panicked at ‘Bitcoin API is disabled’, canister/src/lib.rs:237:13”
May I ask what causes it?
This is a known issue and will be fixed with an upcoming release. Thank you for the note!
Why do I get the same error?
Bitcoin API is disabled
This issue did appear a few months ago but was fixed with a subsequent update. We will report it again, thank you!
I have the same situation now.
It appears this issue has not been solved yet. Is there an estimated time for it? Our product is affected by it and many of our users complained about it. If there is no plan to solve the issue in near future, please let me know as well so that we can remove the feature related to cktestBTC.
Thank you.
2 Likes
I will check back and follow-up!
This is currently a known issue. DFINITY is working on a solution to resync the testnet canister. A governance proposal for the update will be available soon.
Here is an update:
1 Like
Hello, I have noticed that ckTESTBTC still hasn’t returned to normal. Is there any latest news on this?
The second and final proposal to rebootstrap the Bitcoin canister was executed yesterday: https://dashboard.internetcomputer.org/proposal/133319.
I will check to see if there is any other step in the update.
What is the error that you are getting? When was the last time that you got the error?
Just now… 
Thank you for sending over. Will let the team know and will report back.
Okay, thank you for your response. This issue has been going on for almost a month. Many of our users have their testBTC stuck inside, unable to withdraw or bridge…
The problem is that Bitcoin testnet (testnet3) has been behaving very erratically for a while. In the last month, the block rate of bitcoin testnet is ~50x higher than bitcoin mainnet, with crazy “block storms” where the block rate is even higher. Our bitcoin integration was designed for bitcoin mainnet, but testnet behaves so differently, the bitcoin integration at times can’t keep up with bitcoin testnet.
The bitcoin community is discussing this problem and considers making “testnet4” the default new bitcoin testnet. On the ICP side, we have to consider how we move forward. I believe that perhaps there’s more value in switching already to testnet4 rather than sticking with the problematic testnet3.
2 Likes
Hello Eric,
Followed up with the team.
After the second proposal is executed, the Bitcoin canister still needs to continue to sync as noted in the process here. https://dashboard.internetcomputer.org/proposal/133308
We hope that it will fully sync soon and will update everyone looking to use it as soon as possible once it is.
Hello jennifertran, thank you very much! testBTC has finally returned to normal!
1 Like