event icon indicating copy to clipboard operation
event copied to clipboard

External account no addresses

Open xmready opened this issue 9 months ago • 16 comments

Describe the bug

I have three external watch only accounts and I cannot seem to generate receive addresses for them or even view their addresses. I confirmed the addresses were correct when importing the watch only accounts. When I click "Receive" on them, I get the following message with nothing below it:

Image

Reproduce

  1. Import external watch only account
  2. attempt to generate a receive address for it

ZEUS version

v0.10.0

Node interface

Embedded LND

Network

Clearnet

Device

Pixel 7

Device operating system

GrapheneOS 2025032100

Log output


xmready avatar Mar 27 '25 00:03 xmready

Hmm, no problems on my end with my existing wallet and v0.10.0.

Do all three accounts have a | char in their names? Wonder if that could potentially be breaking things somehow.

kaloudis avatar Mar 27 '25 00:03 kaloudis

Hmm, no problems on my end with my existing wallet and v0.10.0.

Do all three accounts have a | char in their names? Wonder if that could potentially be breaking things somehow.

No, they do not all contain the vertical line character. See below for another example:

Image

xmready avatar Mar 27 '25 00:03 xmready

Did you specify Master Key Fingerprint or change the Address type at all?

kaloudis avatar Mar 27 '25 00:03 kaloudis

Did you specify Master Key Fingerprint or change the Address type at all?

No I did not specify a Master Key Fingerprint. I provided a taproot extended public key and selected the corresponding taproot address type. All the addresses matched when I was confirming the import. I tried doing a rescan and restarting the wallet, but now I am missing my latest transaction and it still doesn't work.

xmready avatar Mar 27 '25 01:03 xmready

fwiw if you had funds on there already, you need to hit the Existing account (has funds already) toggle and specify the birthday block height and address count. Rescanning won't be helpful here otherwise.

kaloudis avatar Mar 27 '25 01:03 kaloudis

fwiw if you had funds on there already, you need to hit the Existing account (has funds already) toggle and specify the birthday block height and address count. Rescanning won't be helpful here otherwise.

I didn't have any funds on the watch only wallets, they are new. When I say I lost my latest transaction after a re-scan, I meant a transaction for the Zeus on chain wallet, not for one of the watch only wallets. Sorry for that confusion.

Now that i'm thinking about it, I don't remember if I specified the fingerprint or not when importing. All I know for sure is I provided an extended pub key and chose the correct address type. Wish it just worked.

xmready avatar Mar 27 '25 01:03 xmready

Rescanning takes 10-15 minutes, balance starts and 0 and happens in the background. Unfortunately there is no UI indicator, but you can follow along with progress under Embedded node > LND Logs

Need some changes in LND to improve the UX here https://github.com/lightningnetwork/lnd/issues/8781

kaloudis avatar Mar 27 '25 01:03 kaloudis

Okay thanks for the info. I am still not able to generate addresses for my external watch only accounts. Getting the same problem. When it asked me to confirm the addresses on import everything looked good. Not sure what is the problem here.

xmready avatar Mar 27 '25 01:03 xmready

I just performed a totally clean install of Zeus and recovered my wallet using the seed. I waited for setup to fully complete. This fixed my missing on chain transaction, but did not fix the watch only wallet problem.

I'm still getting the same error/problem when trying to generate receive addresses. I used the master public key, I entered the fingerprint, and selected the address type. Same result as before

xmready avatar Mar 27 '25 22:03 xmready

After flashing a totally fresh install of grapheneos, I did yet another seed recovery in a fresh install of Zeus v0.10.2. I am still getting the same problem described in the OP when adding an external watch only wallet using a taproot public key.

@kaloudis have you tried replicating this issue with a taproot pub key? Is there anything I can do to help squash this bug?

xmready avatar May 16 '25 17:05 xmready

After flashing a totally fresh install of grapheneos, I did yet another seed recovery in a fresh install of Zeus v0.10.2. I am still getting the same problem described in the OP when adding an external watch only wallet using a taproot public key.

@kaloudis have you tried replicating this issue with a taproot pub key? Is there anything I can do to help squash this bug?

I tried w a Taproot pubkey and was unable to recreate.

On your Graphene install do you have sandboxed Google Play Services enabled?

kaloudis avatar May 16 '25 19:05 kaloudis

After flashing a totally fresh install of grapheneos, I did yet another seed recovery in a fresh install of Zeus v0.10.2. I am still getting the same problem described in the OP when adding an external watch only wallet using a taproot public key. @kaloudis have you tried replicating this issue with a taproot pub key? Is there anything I can do to help squash this bug?

I tried w a Taproot pubkey and was unable to recreate.

On your Graphene install do you have sandboxed Google Play Services enabled?

I have the sandboxed play services installed in the "private" section of android 15 in grapheneos. The sandboxed play services doesn't start unless I unlock the private section, which I think is a separate user space and the apps from my user profile can't talk to private apps. Zeus is not installed in private so it is separated from play services.

On my previous grapheneos install I had play services installed in a completely separate user, and I had the same problem with external accounts.

xmready avatar May 16 '25 19:05 xmready

@kaloudis adding to this, I experienced two other bugs when reinstalling that may be related to this.

First, when I performed the recovery from seed, my balance said zero even though I could see the amounts under addresses and I could see all the transactions in my history. I left Zeus open over night and the next day the balance still said zero. It wasn't until I rescanned the main chain wallet from settings that the balance decided to show up.

Second, after a few days, my balance was displaying a duplicate of itself with a clock symbol next to ithe duplicate balance. It has been that way for days now with no sign of going away. See pic below

Image

I can open separate issues for these if you don't think they're related. It seems all these problems share a common theme of things not displaying correctly despite the addresses being correct for the watch only wallet or addresses showing the balances for main chain wallet.

xmready avatar May 18 '25 16:05 xmready

@kaloudis adding to this, I experienced two other bugs when reinstalling that may be related to this.

First, when I performed the recovery from seed, my balance said zero even though I could see the amounts under addresses and I could see all the transactions in my history. I left Zeus open over night and the next day the balance still said zero. It wasn't until I rescanned the main chain wallet from settings that the balance decided to show up.

Second, after a few days, my balance was displaying a duplicate of itself with a clock symbol next to ithe duplicate balance. It has been that way for days now with no sign of going away. See pic below

Image

I can open separate issues for these if you don't think they're related. It seems all these problems share a common theme of things not displaying correctly despite the addresses being correct for the watch only wallet or addresses showing the balances for main chain wallet.

Not related. This pertains to how we fetch blockchain data via Neutrino. Modifying your Neutrino peers and rescanning can help remedy. See https://docs.zeusln.app/for-users/embedded-node/faq/#im-having-issues-broadcasting-on-chain-transactions-they-are-either-disappearing-from-my-wallet-or-not-showing-up-on-a-block-explorer

kaloudis avatar May 18 '25 16:05 kaloudis

Not related. This pertains to how we fetch blockchain data via Neutrino. Modifying your Neutrino peers and rescanning can help remedy. See https://docs.zeusln.app/for-users/embedded-node/faq/#im-having-issues-broadcasting-on-chain-transactions-they-are-either-disappearing-from-my-wallet-or-not-showing-up-on-a-block-explorer

If I'm reading the docs correctly the balance not showing is remedied with a rescan, but I'm still not sure what the yellow clock means. All my transactions have been confirmed on chain a long time ago.

I really appreciate the work you do on this app and I really want it to be my only mobile wallet, but considering I haven't been able to just use it and have it just work especially after multiple fresh installs (yellow clock has happened before) I'm starting to feel a little defeated here.

xmready avatar May 18 '25 17:05 xmready

@kaloudis I did another rescan + restart to try and fix the yellow clock issue and after leaving Zeus open for hours I had no transaction history, the main chain addresses had no balances, and the main screen showed a zero balance. I ran the rescan again to see if that would fix it, and again after a few hours I had no transactions, no address balances, and no balance on the main page.

So again I wiped out the app data and ran a seed recovery and after checking back in a few hours I see my transaction history, I see the address balances, but the main page balance still says zero. This is the same exact behavior I encountered last time I did the recovery, so at least this bug is consistent.

Again I tried a wallet rescan + restart to fix the zero balance after recovery issue and it worked. After attaining this rare situation in Zeus where I can see my balance with no problems or warnings, I swept the on chain balance to Phoenix wallet which seems to be restoring and working without error. I will perhaps return to Zeus in the future to see how it is coming along. For now I would like to spend my time using Bitcoin, not troubleshooting. If you need anymore information or logs from me to help squash the bugs just let me know. Thanks again.

xmready avatar May 20 '25 16:05 xmready