pull down to refresh

2 sats \ 3 replies \ @rizful_com OP 18 Oct \ parent \ on: Receive-only Lightning checkout: a hacked server can’t drain your node lightning

Right. You withdraw/spend from your connected NWC wallet -- could be Alby Hub on your own machine, Alby Cloud, Rizful, or lots of other options -- see here: https://openreceive.org/get_a_nwc_code_to_receive_payments

The point is, from the perspective of the "merchant website" -- where you actually take payments -- it's a one-way system where you can receive but not spend.

Then you use a totally separate system to withdraw. It's a basic "separation of concerns" design, which in the end yields a merchant website which "can't be hacked"....

write
compose
20 sats \ 2 replies \ @anon 18 Oct

but then is it custodial from the OpenReceive server PoV? I don't understand

And another question, if openReceive.org goes down, you're money is gone?

reply
2 sats \ 1 reply \ @rizful_com OP 18 Oct

"but then is it custodial from the OpenReceive server PoV?"

  1. No. You can use any NWC back-end. For fully self-custodial, use Alby Hub on your own hardware. Remember -- your application running OpenReceive holds NO funds. It only allows the deposit of funds into a NWC back-end that you specify, and that you can switch anytime.

"if openReceive.org goes down,"

  1. No. OpenReceive.org is just a website hosting documentation about OpenReceive. It doesn't hold funds, doesn't interact with your server, and has no impact on your merchant process. It's simply hosting docs as a helper for this open-source project: https://github.com/OpenReceive/openreceive
reply
2 sats \ 0 replies \ @StealthEntropy 19 Oct

So AlbyHub and Rizful are just NWC services?

reply