Does this not work for you? Why do you need to edit an existing connection?
I'll try this. Is the PubKey sufficient to connect? There don't appear to be full secrets generated
reply
43 sats \ 8 replies \ @ek 8 Sep
No, it should look like this:
nostr+walletconnect://00f1646918f62a929f7bb62a3dd8404ed5bed8e5e1a8857d09de65f854d28976?relay=wss://relay.getalby.com/v1&secret=990a489309d362d8957e206a33f1dd062e676897d8759943559a0e49604fafcb&lud16=brilliantpresence748547@getalby.com
This is a connection that my Alby Hub generated that I am going to throw away now.
reply
I know. Are you using the Alby Hub with its node, or your own node? I am using my own node. I don't get access to the full secrets when I connect to SN on the hub.
reply
43 sats \ 6 replies \ @ek 8 Sep
I am using a Cashu mint since I only use it for testing.
You mean when you copy the secret, it does not start with nostr+walletconnect://?
reply
Edit: Forget that. Let me try again. I had a senior moment.
reply
43 sats \ 4 replies \ @ek 8 Sep
I am cheering for you
reply
It worked! Thanks for your patience. I do wonder, though, why Alby's NWC connect standalone app doesn't seem to allow you to edit permissions? cc: @Alby
reply
43 sats \ 2 replies \ @ek 8 Sep
No worries, I think you have more patience with us
I was using the Alby hub standalone NWC connect app I have on my node. Now I'll try the actual Alby Hub SN connection.
reply