reply on: Receive Wallet error \ stacker news ~AskSN

pull down to refresh

34 sats \ 25 replies \ @k00b 30 Jan \ on: Receive Wallet error AskSN

Off the top of my head, two reasons why this can happen:

you are withdrawing from one SN account to another SN account or you are zapping someone on SN via withdrawal from SN
you have attached another SN account via lightning address as a receiving method

If you have multiple receiving methods, that'd explain why it's eventually succeeding. Receiving and sending have fallbacks, we try each receiving wallet until one succeeds.

16 sats \ 16 replies \ @itsMoro OP 30 Jan

hmm i dont think i have either of those scenarios happening 🤔

31 sats \ 15 replies \ @k00b 30 Jan

This error occurs when we wrap the invoice for proxying and I've only ever seen it when we are asked to proxy an invoice to SN itself. But there might be an edge case here that I'm not considering.

0 sats \ 14 replies \ @itsMoro OP 30 Jan

i sent a 5 sat zap to myself from a burner npub using a coinos account. i immediately receoved 100 sats into my attached SN wallet, perhaps from other stuck zaps. very odd 😅

34 sats \ 13 replies \ @k00b 30 Jan

I FIGURED IT OUT

Your node is private and SN's node is a hop hint!

I'm guessing you're peered with us. There's probably an exception we need make.

1100 sats \ 3 replies \ @itsMoro OP 30 Jan

i am peered and have a channel with stacker news

50 sats \ 2 replies \ @k00b 1 Feb

Okay, looks like the fix works.

Thanks again. I wouldn't have caught it - we weren't using private nodes in our regtest setup.

view all 2 replies

0 sats \ 8 replies \ @itsMoro OP 21h

another potential bug sorry...

i want to connect my nwc receive option. i attach my read only nwc string, and in the logs,it shows success:

however, on the wallet page it shows receive as red.

and when i send sats to my stacker news ln address with this receive option, it goes straight to CCs. it does not appear to have successfully attached, however logs say otherwise. there is no message in the logs regarding the sats i sent too, makes me think its not actually attached at all.

34 sats \ 7 replies \ @k00b 19h

I’m confused why it’d show red if it succeeded. The status is derived from the logs. It might be best to detach it, clear the logs, then try again.

view all 7 replies

0 sats \ 1 reply \ @ama 30 Jan

I don't do any of those two things and also see the same error.

0 sats \ 0 replies \ @k00b 30 Jan

Does your node only have private channels? We need to make an exception. I'm opening a github issue now. I should be able to get a fix in soon.

0 sats \ 5 replies \ @k00b 30 Jan

Another reason why it may eventually succeed is that we try proxying first (fails), then try without (succeeds), depending on your settings.

You say you're running two nodes? Sending is lnd and receiving is another lnd?

1579 sats \ 4 replies \ @itsMoro OP 30 Jan

i have a core lightning node i dont connect to anything to that i can test send to my SN ln address, then i do all the funny business with my lnd node ( connecting for sending / receiving in sites like SN or nostr)

47 sats \ 3 replies \ @k00b 30 Jan

Right on. I'll see if I can make an exception when we're a hop hint. Thanks for surfacing this.

0 sats \ 1 reply \ @itsMoro OP 30 Jan

if i set it up like this for now, should try direct deposit to nwc first, then direct deposit to ln address second, before it deposits into CCs, ya?

28 sats \ 0 replies \ @k00b 30 Jan

Yep exactly like that

0 sats \ 0 replies \ @itsMoro OP 30 Jan

you're welcome. ya my LND node has just two private channels open, one being with Stacker News