ckBTC Retrieve BTC stuck: Txid updated by Minter but still not broadcasting (36+ hours

Developers internet-identity
1

While analyzing ckBTC retrieve transactions, I noticed that several block indexes (3459007, 3459009, 3459013) appear to be stuck for over 29 hours.

The Minter has already generated a new Txid (f69e339597b98a3286f586785c33b320f38ff4d2921f07dafecd12de881b769d), but it still cannot be found on the Bitcoin mainnet (mempool.space).

I’m trying to understand the underlying reason for this delay. Could it be related to fee estimation or possibly an issue with a legacy address (1Aur…) included in the batch?

I would appreciate any clarification on why these block indexes remain pending for such a long time.

2

Thanks for reporting! We’re looking into it.

3

Hello, may I ask if there has been any progress with the investigation?

4

Sure. The problem is that the created transaction is invalid because it attempts to consume an output that has already been spent. We’re now looking into how this happened and then propose a fix.

Note that no funds are at risk. It just may take some time to get them unstuck.

5

Hey, any updates today?

6

We are now working on a fix, which will trigger a valid transaction to be sent so that the withdrawals will (finally) go through.

We’re hoping to have a proposal to upgrade the ckBTC minter ready in the next few days.