pull down to refresh

at one point i connected an embedded LND Zeus wallet to nostr via NWC, and zaps wud come into zaplocker consistently, but zapping others wudn't work; it was a receive-send NWC configuration;

i then attached a Rizful wallet via NWC (send-receive configuration) into another nostr client, while keeping the Zeus-NWC attachment in the original client - zaps continued coming into the Zeus-zaplocker, and redeeming them was straightforward; the LN address was set as Zeuspay;

i cud also start sending zaps from Rizful...

how did this split occur? how do i fix the issue of sending zaps from Zeus via NWC connection?

Gracias sensei!

Zeus have 3 options for receiving zaps to a LN address:

  • zaplocker (hold invoices)
  • cashu mint (redeemable tokens into a cashu wallet or straight to your own LN channels))
  • recently introduced FW to a NWC account (straight to your LN node of desire over NWC)

It's up to you which one you want to use.

reply

thank u for the reminder - i see the major updates and have yet to experiment with the mints & forwarding;

it's still unclear to me how the piping worked in the configurations setup i have described; i think the main issue is the send from Zeus-NWC: persistent mode doesn't quite work, but maybe i have to tinker with background process settings a little bit;

it is a nifty trick tho - receiving into one NWC wallet type and sending out of another;

reply

I suggest to use LDK node if you use NWC sub-accounts. It syncs faster.
And you have 2 "persistent modes": one for the node and one for the NWC service. I wrote a guide on SN few months ago, see in my bio.
LND nodes are more for advanced users for specific cases.

reply