do you add a lud16 to the connection string? otherwise damus won't set it up on their profile.
Discussion
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=