I don't see how that's possible. You have your Cashu address set in your profile so any zaps should go to Cashu. There's no pathway to Coinos since you're not using Coinos address. Unless Damus is somehow ignoring the address you have set In your profile and is routing everything through NWC? But I've never heard of such a thing. Double check your Cashu Wallet.
Discussion
Right! My inbound profile address is my new npub but my NWC is coinos. In theory I should be able to zap myself from coinos to cashu - but it goes straight out and back in via coinos!
Wow. Then Damus is actually ignoring your zap address and routing everything through your NWC. As I said, I've never heard such a thing. I'll tell you, after all this nonsense, I'm starting to dislike Damus. First it's not working with Cashu, and now it's ignoring the protocol and routing everything through NWC. This is disturbing all the way around.
Hey, nostr:nprofile1qqsr9cvzwc652r4m83d86ykplrnm9dg5gwdvzzn8ameanlvut35wy3gpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3qamnwvaz7tmwdaehgu3wwa5kuegpz4mhxue69uhhyetvv9ujumt0wd68ytnsw43q3ttcfs, could you help shed some like on this situation? We're pulling our hair out trying to get Cashu Wallet via NWC working with Damus and everything seems to be going wrong despite it working fine with other clients.
And now it seems that Damus is ignoring the LN address he's got set o his profile and is routing all outgoing AND incoming zaps through NWC?
that doesn't make any sense. damus does not "route zaps through nwc" whatever that means.
That's what I thought. But he's got his Cashu Wallet LN address set I his profile, and Coinos set as NWC, but when I zap him his goes to Coinos. I don't know how else to explain that.
And when he tries to zap himself, in instead of going from his Coinos to his Cashu, it's just being sent from Coinos and then received by Coinos. It's as if the LN address he's got set in his profile is being completely ignored and somehow his Coinos address is being used as both his LN address and his NWC.
do you add a lud16 to the connection string? otherwise damus won't set it up on their profile.
sounds like the NWC connections hasn't switched over to the new one? first time hearing that bug.
What do you recommend? Should I have him re-paste the connect string into Damus?
Yes, but cashu should add lud16 if they want clients to automatically set up the receive address, otherwise they will continue receiving zaps to their existing address. I added this to NWC for this exact reason
So that would mean that if Coinos included the lud16 in their connect string Damus would use the associated Coinos LN address to receive instead of whatever LN address was set in the profile?
OK, so I looked at the Coinos connect string and it does include the lud16. That means the Damus is using that instead of the defined LN address from the profile (the Cashu address). If we manually add the Cashu lud16 to the Cashu connect string and paste that into Damus, it should work properly then, correct? Because that makes a lot of sense based on what you've said.
I'm going to have him do that and we'll see if the problem goes away. Thank you very much for taking the time to help with this problem. I appreciate your expertise and assistance.
The NWC connect string was copy/pasted directly frokm Cashu without alteration. It looks like this:
nostr+walletconnect://c6287894d0731059634ba912930f4557dd41ca7be1f32d6cacf398288125e361?relay=wss://relay.primal.net&relay=wss://relay.damus.io&relay=wss://relay.8333.space/&relay=wss://nos.lol&secret=