BackStory
Bit of background, I had a channel open to Olympus by zeus to begin with (what the wallet prompts the user to do to create first liquidity). That channel was open for many months working just fine.
Recently I created a 2nd channel to another lightning node (not Zeus), to increase payment paths and test the open channel function.
Fairly soon after opening the 2nd channel was open the first channel was closed (not by me).
Maybe zeus does this once it sees the user has graduated to opening channels by themself or maybe just a coincidence.
Issue
The first channel was closed and I have the correct onchain BTC in my zeus wallet. However there is a Pending Balance of 3,000 Sats. When I look under onchain/Coins I see the two transactions, 1 for the balance of the closed channel and a 2nd one for 3,000 sats.
This 2nd transaction has a Transaction Hash but when looking in the mempool for this it is not found and is likely why it is showing as pending in Zeus.
This pending balance has been there for several weeks at this point and I would like to get in cleaned up so I don't have it showing up.
Any help is appreciated.
Generally speaking for failed txs with Embedded LND you would want to do this: https://docs.zeusln.app/for-users/local-wallets/embedded-lnd/faq#im-having-issues-broadcasting-on-chain-transactions-they-are-either-disappearing-from-my-wallet-or-not-showing-up-on-a-block-explorer
In this case, you would likely have to force close the channel after as funding didn't complete in the time required.
If you go to Tools > Developer you can find the AbandonChan function and drop the pending channel as long as you're certain it hasn't been broadcasted.
Moving forward, either make sure you audit your Neutrino peers or move over to the new Esplora-backed LDK Node wallet if you keep having this issue.
The Rescan solved my issue.
Thank You
I have random question here. Rescanning requires you don't close the app. Do you try to prevent your phone from sleeping during rescan? Because some time ago i was forced to dl that for an hour, otherwise everything got buggy and rescan didn't find all my utxos.
Countrary to the aggressive contradiction by some people on this forum, Zeus is buggy as HELL.
This is unfortunately just the nature of the Neutrino chain backend LND mobile has.
Our new default wallet is LDK Node and doesn't have this issue.
Can an user migrate a wallet from Embedded LND to LDKNode?
Or is it just easier to spin up a fresh LDK Node wallet and transfer founds?
Unfortunately the databases are incompatible. Easiest to just send funds over.
If you're an LSP customer, contact support and we'll give you credits for new channels though.
Hm... I would suggest Zeus itself track these things. For example if a transaction appears and then disappears it has two entries in the log (one credit and one debit, explaining that the transaction disappeared for example). Also Zeus can see if its calculated ballance differs from the one lnd reports and either prompt the user to check what's up (with steps) or if possible automatically fix the issue.
Thanks, but you're fundamentally misunderstanding the issue. The records are fine, it's the broadcasting to the mempool that is the issue here.
Hmm you can email Zeus support;
support@zeusln.com
And let all the Stackers miss out on my fun? :)
Darth is gone and Evan isn’t on here much. I noticed it got zapped but no comments.
this
Interseting side note. I have had two different:
On this post.
In my personal experience I do Not get many of these.
I don't know how or why people found this post but I am glad I posted it if got two new Stackers.