Wallet syncing 50% for 3 days now

Technical Questions
,
1

GM team, my wallet has been syncing at 50% for the past half a week. It also resets itself and this forces me to enter a seed phrase everytime I intend to use it. Kindly advise.

2 Likes
2

Please report the issue to the lace team. They manage the wallet.

3 Likes
3

Thanks. I was not aware :slight_smile:

2 Likes
4

It looks like there is an issue with the wallet after a certain amount of transactions, for now, I would open a new wallet to continue testing.

3 Likes
5

This stuck syncing at 50% is happening here as well, with two brand-new wallets with zero transactions. Also happens using the midnight-local-network docker images.

2 Likes
6

Is there any word from the Midnight team on this `wallet sync stuck at 50% issue`? I am developing a dApp and need this fixed in order to test. My lace midnight wallet has been stuck at 50% for days. I’m using the Google Browser extension as recommended. I’ve turned the extension on and off. I’ve tried resyncing the wallet. This is my third wallet as well. Nothing works. It seems this issue started in December 2025 and it is now February 2026. This is a core function and should be tackled immediately. I’m a dApp developer for EVM chains, and wallet functionality is foundational to our work and not something we should have to worry about. Any idea of when this will be addressed and actually fixed?

7

I just want to say thank you to Coinbox for answering me and helping with this sync issue. For those who might run into it, here is something to try:

”A wallet sync stuck at 50% is often related to a node connection or local data corruption rather than the wallet itself, so a reasonable first step is to clear the extension’s cached blockchain data or switch the wallet to connect through a different network endpoint or fresh browser profile to rule out environment conflicts. If the issue began around a specific release period, testing an earlier or beta version of the extension in an isolated setup can help confirm whether it’s a regression tied to recent updates, which would guide whether you should wait for a patch or apply a temporary workaround for development testing.”

1 Like