New version rolling out now, 0.6.6.
This fixes some issues with channels and temporarily removes the internal swap functionality that was causing the device to lock up. We will turn it back on when we can reproduce and fix the issue.
For all issues, please provide as much info as possible with logs and submit here: https://github.com/mutinywallet/mutiny-web/issues
Since the last update to nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg android app version 0.6.6 I constantly get an time out error. I can reload the wallet which will open it again, but after 30 seconds the error shows up again.🤔
Could you submit an issue and upload logs?
No, sending and receiving still work. It just relates to when trying to go directly from fedimint to a self custodial channel. Something is screwing up for some users and we haven't figured out how to reproduce it yet. Works most of the time, but in some rare cases it critically fails so we have to turn it off.
New version rolling out now, 0.6.6.
This fixes some issues with channels and temporarily removes the internal swap functionality that was causing the device to lock up. We will turn it back on when we can reproduce and fix the issue.
For all issues, please provide as much info as possible with logs and submit here: https://github.com/mutinywallet/mutiny-web/issues
Self custody lightning goes through the LSP, which is having issues.
Our LSP isn't working so well these days, would not recommend it.
The only other wallet we heard of with issues is Blink but besides that, they should work. Let us know if there's any other issues.
Strike, and by extension primal, cannot send to federations at this time. We're working with them on it.
I've been trying to use Strike (Android) to send to nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg and it keeps failing with "can't find payment route". Anyone have any ideas?
I'm just trying to get some BTC into this thing
Do you have a federation added in mutiny?
nostr:npub12vkcxr0luzwp8e673v29eqjhrr7p9vqq8asav85swaepclllj09sylpugg can I use nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg instead of the built in one while using your app?
On Android you can, in the wallet settings of their app.
We haven't handle this yet, on the Todo list.
We're working on that right now. Really appreciate your thoughts there!
There's another open issue around payment info lookup that's causing slowness with federations. Thanks for testing this!
I've been playing with nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg some more. I like the idea of starting with #ecash and moving into #lightning later. This could be a good next step after something like WOS. There's a path forward from custodial to self-custody all in one app. I like the #Nostr integration, too, other than having to share the private key.
Thank you!
On the web, we do work with nostr browser extensions too. That's one way to use it without sharing the nsec.
On Android it used to be in the wallet settings. They don't support it on iOS anymore.
0.6.5 rolling out now which fixes an issue with the bitcoin atlantis federation. If you had this issue, please let us know if it was fixed after you update. Thanks to everyone that submitted logs and described their situation.
Multiple people have reported issues with that federation. If you can chime in and provide logs, that would be helpful.