pull down to refresh
121 sats \ 13 replies \ @BTCLNAT 29 Oct \ on: Getting started with Walletano bitcoin_beginners
Hi. I've had 2 issues with the custodial wallet.
-
The PIN option doesn't work.
-
I made 2 deposits of 10 SATs each to test invoice and LN address and both OK. Now I try to send back to the same source wallet to test the withdrawal and it gives me an error. I made the attempts both by invoice and by LN address, with 15 SATs, 10 SATs and 5 SATs. Always ERROR
reply
Thanks for this detail!
I updated my guide on github with your mention.
search in Google recovery walletano
LOL what?
You never read their FAQ and right on the front page is mentioned?
https://www.walletano.com/wallet/wallet_recovery.html
Why do you have to "google recovery" when is right before your eyes?
So this could be a bug to force people to use an email for recovery just to be able to send sats. Indeed, I have an email confirmed for recovery in my walletano account, but that is nowhere mentioned as REQUIRED.
This is strange, seems like a bug.
@walletano ?
reply
reply
My point is to NOT use any search engine on internet about "recovery".
You have 99% chances to get a wrong link that will fuck you out. This is how people get rekt and lose their sats, by "googling".
ALWAYS go and read the original page FAQ and instructions.
Is right there on the main Walletano page!
I just zapped you from a walletano account. Worked perfectly fine.
You guys down there are totally isolated and censored, sorry.
reply
When I try to zap you to SN, it doesn't show your LN address, it keeps the @walletano.com domain.
reply
If you already insert another LN address and click on send, it will send to that one.
The bellow @ walletano.com one is additional if you want to send to that one.
reply
idk, I saw somebody else having the same error, must be something with your connection through a VPN or something like that.
I have 0 issues paying.
reply
reply
try to use a desktop browser and when you get that error, press CTRL+SHFT+I
Then you can see the details of the error in the debug console.
reply