pull down to refresh

I think the solution is to separate send/receive into independent steps as we've discussed.
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
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