pull down to refresh

65 sats \ 14 replies \ @0xbitcoiner 19 Dec \ on: SN resolves to go noncustodial on Jan. 3rd - FAQ & AMA
I'm testing an alternative to alby, in NWC you have two connection strings, one for sending and one for receiving. For now I've only tested sending and it worked. My question is whether it's the same string for receiving or a different one. Coinos only offers one string. I followed @realBitcoinDog's tutorial and he doesn't mention this, he uses LN address to receive. cc/ @ek
write
preview
33 sats \ 5 replies \ @rizful_com 19 Dec
This is the one of the must confusing things about NWC with Stacker News currently. We've discussed with @koob and it's likely this behavior will be re-worked in the future, but for now, you need TWO DIFFERENT NWC STRINGS.... Our guide is here for Rizful but it should also work for other NWC back-ends like Alby Hub and others..... https://rizful.com/docs/use-rizful-with-services#use-rizful-with-stacker-news
reply
0 sats \ 3 replies \ @ek 19 Dec
it's likely this behavior will be re-worked in the future
Do you have suggestions? I think this is a limitation of how NWC is generally used since we don't want to store spending permissions on our server.1 So afaict, we need two separate connections since one needs to be on your device or encrypted on the server and one needs to be in plaintext on the server.
I think all we can do is to explain this better but wallets will continue to have to provide two different strings unless the spec is updated in some way. 🤔

Footnotes

  1. and nobody should if they want to claim they are non-custodial ↩
reply
0 sats \ 2 replies \ @k00b OP 19 Dec
I think the solution is to separate send/receive into independent steps as we've discussed.
reply
0 sats \ 1 reply \ @ek 19 Dec
ah yes, independent steps can explain it better but we will still need two different NWC strings so I was replying to the "for now" in
but for now, you need TWO DIFFERENT NWC STRINGS.
reply
11 sats \ 0 replies \ @k00b OP 19 Dec
I guess we can add an explainer in the short term.
Why do we need two separate stings? XYZ app lets me use just one.
We don't ever store spending permissions on the server. To enable receiving, we need a string without spending permissions for the server. To enable spending, we need one string for that never leaves your browser.
reply
0 sats \ 0 replies \ @0xbitcoiner 19 Dec
cool! when i have a bit more time i'll try it out.
reply
44 sats \ 3 replies \ @ek 19 Dec
For receiving, you need a different string because we need to store it in plaintext on the server to coordinate payments.
@adam_coinos_io, does Coinos provide separate NWC strings to send and receive?
reply
61 sats \ 1 reply \ @adam_coinos_io 19 Dec
No we don't currently but I can look into adding it
reply
11 sats \ 0 replies \ @0xbitcoiner 19 Dec
that was the icing on the cake. Let us know when you have something ready. thanks!
reply
0 sats \ 0 replies \ @rizful_com 19 Dec
Correct.
reply
22 sats \ 2 replies \ @ek 19 Dec
But if Coinos gives you a lightning address, you can use that. It doesn’t matter which receive method you use; we handle them all the same.
reply
44 sats \ 1 reply \ @0xbitcoiner 19 Dec
This is how I have it set up at the moment (LN Address to receive) and it works. I'm asking more out of curiosity. Maybe it doesn't matter if it works with SN, but maybe it does with other platforms. Let's wait for adam's reply. Thanks!
reply
33 sats \ 0 replies \ @ek 19 Dec
Cool, thanks for letting us know it works for you!
I also recently mentioned the UX issues with NWC here, maybe something will come out of it.
reply
0 sats \ 0 replies \ @realBitcoinDog 19 Dec
I’ll be curious for the answer!
reply