You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Even when enabling these in Server Settings, I still get an error, though a different one. You cannot send from a cold wallet which doesn't seem to be true, since I do have a hot wallet generated on the app, but I guess in the eyes of the server it's not a hot wallet, still a server shouldn't be able to decide on this.
I've consolidated what we have in the Wallet vs. Send views and on the latter sending now works from the app's wallet.
For now, external wallets (connected on the server, hot or watch-only) aren't supported and we show this hint to the user until we start to supporting hot wallets connected on the server:
@pavlenex I think we should move this one out of the first milestone into the stage in which we plan to support external hot wallets on the server. For the beta we have the warnings shown above and the ability to send from the app's internal wallet.
Sending on-chain funds from the app generated wallet requires for some reason hot wallets to be enabled on the server? Is there a reason for this?
To replicate:
user 1
anduser 2
user 1 wallet
User 2 app
, generate invoiceuser 1 app
touser 2 keypad
The text was updated successfully, but these errors were encountered: