pull down to refresh

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.
i am peered and have a channel with stacker news
reply
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.
reply
well, i did not have the proxy checked as 'on' since we chatted. ill turn it on now, see if it works now.
reply
i sent a couple test zaps to myself from coinos account. worked, and my node is no longer reflected as the receiving node ( shows stacker news) so the proxy is working too 🤙
thanks for the quick fix!
reply
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.
reply
34 sats \ 7 replies \ @k00b 1 Feb
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.
reply
i cleared the logs and reattached the nwc. now it shows green for the receive arrow, however my test send had the same result ; did not show any activity in wallet logs, sats went straight to CCs.
reply
0 sats \ 5 replies \ @k00b 1 Feb
How many sats was your test?
reply
5 sats
reply
0 sats \ 3 replies \ @k00b 1 Feb
Ah that explains it. In settings there are dust limits. The default is 10 sats.
Sorry everything is spread around. We desperately need to do a pass over the UX here.