pull down to refresh

I have been using the feature that allows switching between accounts. If I use the same attached wallet for both accounts, I notice that the failure rate for zaps using the second account is very high. It doesn't seem to matter what attached wallet I use. I guess I can just use separate wallets for each account, but I wonder if this is intentional?

196 sats \ 2 replies \ @k00b 15h

I'm looking into this now. As opti said, I have some related bug fixes sitting.

Another thing to consider: if you are testing this by zapping your other account with the same underlying node, you maybe be self-paying, ie nodeA pays nodeA, and your node might reject self-payments.

I'll hunt for a bug here though.

reply
119 sats \ 0 replies \ @optimism 10h

First way I tried to repro this on dev env was with self-paying and that worked instead of repro the bug (with lnd_nwc posing as alby on regtest) while in every other case I get that payment-to-self error.

reply

If it helps, I do not zap my other account beyond a genuine accident once in a while.

reply
158 sats \ 8 replies \ @optimism 22h

Failures are only intentional if they come with a popup telling you that "you cannot do this, bro". So let's assume bug.

If I use the same attached wallet for both accounts
  1. Which types of wallet connections did you try? (nwc/cln/lnd/lnbits/clink)
  2. Do you share the connection string (nwc uri / cln rune / lnd macaroon) between the accounts? Or using different ones?
reply
106 sats \ 3 replies \ @DarthCoin 22h

could be also messed up the browser cache.
@siggy47 I would suggest to try using a different browser for each account and see if is doing it again.

reply
37 sats \ 0 replies \ @optimism 22h

Yes. Those are hard bugs. Can still be fixed though. I have a dev env running and I was testing right now so I might as well test and try to reproduce this while I'm at it.

reply

I will try this, Darth. You might be right. It could only be send, not receive, which points to the browser. I can zap about 25% of the time.

reply
58 sats \ 0 replies \ @optimism 21h

This should work around the issue but it still would be good to get it fixed. @k00b does have a PR pending QA that does fixes to a lot of the guts of this so I'll test against that too.

reply

1.Zeus and Alby
2. No. Different ones

reply
37 sats \ 2 replies \ @optimism 21h

Zeus over NWC? Or just the receive function?

reply
70 sats \ 1 reply \ @siggy47 OP 21h

No. Alby. I misspoke.

reply
37 sats \ 0 replies \ @optimism 21h

Ok. I'll mix this into my test plan this morning.

reply
37 sats \ 3 replies \ @grayruby 20h

I use different wallets for grayruby and stackersports accounts so haven’t encountered this issue.

reply

I should do that too, I guess. I wasn't planning on zapping much from satwize, but I was wrong!

reply
37 sats \ 1 reply \ @grayruby 19h

It makes accounting easier too if that matters to you.

reply

I got my accounting right here.😀

All I know is a lot more goes out than comes in!

reply

of course you can't zap yourself.

reply
37 sats \ 1 reply \ @DarthCoin 22h

OP didn't said that. He just use same wallet for 2 accounts.

reply

right.

reply