pull down to refresh
50 sats \ 34 replies \ @nout 20 Sep \ on: Official Coinos Guide meta
The NWC should be usable for both send and receive, right? @phaedrus
No. Other companies might not care but SN does not store the ability to spend your money on our servers.
Just to be clear, because everyone seems to glaze over when we say it, and other companies say we are using NWC wrong: SN does not, and will not, store the ability to spend your money on our servers.
Coinos generates only one NWC string that grants both spending and receiving permissions in the same string. We cannot remove spending permissions from it, so we do not permit coinos' nwc string to be used for receiving. (It being an option was a mistake on our part. It will be removed in a future release.)
reply
Can you clarify what this means?
If I input a NWC string on SN for a sending wallet, in what ways am I or am I not giving SN the ability to spend my money?
reply
in what ways am I giving SN the ability to spend my money: when you have SN's website loaded, your wallet is decrypted, and your browser is connected to the internet, SN's clientside code has the ability to spend your money from your browser.
in what ways am I NOT giving SN the ability to spend my money: when SN's website is NOT loaded in your browser or your wallet is NOT decrypted or your browser is NOT connected to the internet, SN cannot spend your money.
in what ways WOULD I be giving SN the ability to spend my money IF SN did this differently: SN, or anyone who gained access to SN's database, would be able to spend your money at will, at anytime.
reply
It may seem like we're punishing ourselves by being paranoid and doing something that may only sound marginally safer, but we think it's more than marginally safer and worth the pain -- assuming we can smooth out the UX.
Further, establishing the precedent and expertise around not storing any sensitive customer data on the servers will afford us great agility when doing things like end-to-end encrypted DMs (which we see as critical to providing marketplace and private chat/community features worthy of bitcoiners).
reply
reply
reply
I... don't know why. The UX is more steps?
reply
-
They only store credentials to receive on your device, so you can only receive when your device is online (additionally to the requirement that whichever lightning node you use needs to be online). -
They store credentials to receive on their server so your device does not have to be online to receive, but now they need to make sure these credentials do NOT allow spending else they or anyone with access to them can spend from your wallet.
edit: Wait, I said something wrong. They could add NWC for receiving to nostr profiles, and clients could then fetch it and use it to request invoices from your node, but the permissions need to be checked before adding it to your profile for everyone to see.
Sorry, I just woke up lol
Where exactly on the browser is the decrypted wallet stored? And does this mean our NWC is encrypted and living on your database?
reply
reply
Got it. But then where's it come from / get hydrated? Does that mean it's living encrypted on your DB?
reply
reply
Ahhh, the passphrase decrypts it. THANK YOU!
And I guess last question because I have a severe misunderstanding:
in what ways am I NOT giving SN the ability to spend my money: when SN's website is NOT loaded in your browser or your wallet is NOT decrypted or your browser is NOT connected to the internet, SN cannot spend your money.
The encryption key must live somewhere so can't SN decrypt said NWC and spend money that way? Or do I severely misunderstand NWC
lol I had to deeply suck air in when I read this
I wish we could use the same connection for both but no.
Maybe I will have some suggestions for the spec, because the UX around permissions is by far the biggest pain point when it comes to NWC.
reply
The coinos NWC string includes the lightning address (e.g.
xxxxx&lud16=nout@coinos.io), so why do users have to set it up separately? Can't you just parse that and use it?
Is lud16 not what I think it is and the fact that it matches my receive lightning address is just coincidence?reply
reply
reply
reply
