After making a deposit via *Node -> Advanced -> Deposit Bitcoin*, the funds do not show up in the On-chain Balance.

[jpl-btc]

Details:
The address generated in this flow (Node -> Advanced -> Deposit Bitcoin) is not recognized by the "On-chain balance reader", even though the funds are there. I do not recommend anyone to do this but I tested myself and by placing the 12-word seed phrase in Sparrow, the funds are there and the sparrow wallet picks up correctly all UTXOs and the deposited funds.... But not the Alby Hub.

Workaround:
To make the funds reappear in the On-chain Balance of Alby Hub:

1. Go to the channel creation flow.
2. Start the process of creating a channel with on-chain funds.
3. Press the "Refresh" button repeatedly until the same address generated in the advanced->deposit appears.
4. Press "Refresh" once more to generate a new address.
5. This forces the funds to be recognized in the Alby Hub interface and the previously deposited funds now appear in the On-chain balance.

This happened to at least 3 users + myself in the 1.12 version. I am reporting this now because I have not found an issue about this problem, I thought there was.

[rolznz]

@jpl-btc to confirm, this LDK?

I cannot reproduce this.

1. Node -> Advanced -> Deposit Bitcoin and deposit.
2. Go to node page.
3. Wait for 2 minutes for onchain wallet to sync
4. funds show up as expected.

[rolznz]

Related issue: #774

[rolznz]

Press the "Refresh" button repeatedly until the same address generated in the advanced->deposit appears.

Hmm, this does not make sense. The same address should show because it is the first unused address.

[gallizoltan]

@jpl-btc Thank you very much for the bug report – I’m experiencing the same issue. Special thanks for the workaround – it worked for me! 😎

[ratacibernetica]

Happened to me as well.
Using v1.13.0
Safari Version 18.3 (20620.2.3)

The worked around seemed to work. Thanks!

[jpl-btc]

I'm counting 6 users + me so far with this problem
I have seen this happen only with Hubs with v 1.12

Can you tell us which Alby Hub version were you running when you stumble upon this issue, @ratacibernetica @gallizoltan ? Thanks!

[rolznz]

Ah, I see. It's because of the LDK upgrade that reset the bitcoin address descriptor, and we saved the last used address which might be a few addresses higher than the current index.

Thanks for giving the instructions to work around this!

[gallizoltan]

I was using version 1.12 when I encountered this issue. Today, I updated to version 1.13, and I haven’t noticed the bug since, though I haven’t specifically tried to trigger it again.

[rolznz]

Another workaround for v1.13.0: go to settings -> debug tools -> reset router (ALL) and then re-enter your unlock password to restart your node.

[rolznz]

I was using version 1.12 when I encountered this issue. Today, I updated to version 1.13, and I haven’t noticed the bug since, though I haven’t specifically tried to trigger it again.

It should only happen once. This is related to a LDK update which reset the bitcoin syncing address index to 0, whereas Alby Hub saves a last-used address which will be on a higher index, which LDK does not know about and does not sync, until a full re-scan or new addresses are generated until we get back to the previous index.