Yesterday was an unfortunate day for me.
Due to me toying around with Mutiny Wallet somewhat too much, An glitch occured that then makes me barely able to access my wallet.
So back then, i moved my balance from WoS to Mutiny due to interest. Things goes well at the first week until i try to pay an failed invoice for more than 3 times that then when i opened the wallet in other device, I lost 5K of sats (It's the price of that failed invoice. Should be restored by fedimint but this time does not seems so).
Either it's misbehaving fedimint or something messed up in mutiny-node.
So usually, When payment is failed, Mutiny then will restore the balance to my wallet. But if i keep doing it over and over again, which then randomly crashes at the pending stage, Mutiny will not restore my balance for some weird reasons.
That part is where weird things happen. As i try to zap without preserving atleast 1% of my balance (even with fedimint), Sometime fee checking just fails and gives 0 to mutiny. When that happens, I could basically try to send the entire balance of my wallet. But that will make another big disaster, which is what happend to me.
Once the second bug happens, The Fedimint federation that i joined will basically says "no" to every single [send] requests that i want to, and the balance will somewhat recover, except it wasn't and will consume A LOT of memory without reasons, which then leading to crash due to out of memory.
If i try to open again, My balance will looks like it was cutted. The previous sats invoice that pending or failed will never restored to my balance again. If only i try to send sats again, The memory usage will go spike up to 110% and then crashes my app or browser, again.
Trying to open again will make it refresh the balance. But still i will not be able to do anything with it as every single payment attempts that i try will simply gives pending result while the memory usage goes spuking up.
If that happens, congratulations. The only way out is to get out from the federation and use on-chain or other federation.
I could try to resolve this in my laptop by adding swaps. But the problem was my disk is just slow. It was not designed for that.
Even it works i may need to wait from evening to midnight. With many retries after hours of attempts, I am still empty handed. Nothing seems working except reporting the bug to the devs now.

The fact that i could not pay for the server that will end in May 1st is even frustrating. So i had no choice but to end up abandoning it as my mutiny wallet is broken.
Oh boy oh boy. Though it's a cold money, These sats simply gone to nowhere and being barely accessible is terrifying.
You just opened up the issue over the weekend and we need time to investigate. The sats are likely not gone. There's no reason to be freaking out about it.
reply
A week after 5 days of my last performance profiler report,
Nothing.
Still not able to open my wallet as usual, Yet still unable to get 80% of my balance.
reply
Opened back my laptop, and opens mutinywallet, only 4.5K sats of the balance was restored. 20K gone into void.
reply
Till today i could not open mutiny in my phone. It keeps crashing due to out of memory.
reply
i moved my balance from WoS to Mutiny due to interest.
And I supposed that you didn't run your own Mutiny server, as it should be. Moving from WoS to a default Mutiny demo (mutinywallet.com domain) is not too much different than still using WoS.
If that domain goes busted, your funds cannot be accessed anymore. Domains could very easily goes busted. Remember that. Not your domain = not your server.
reply
I am using the mutiny mobile app most of the time.
reply
And did you run your own Mutiny server?
reply
I have no plan to do so yet.
reply
If you use it as a testing ground, is OK. But if you plan to use it for long term, you should seriously considering to run your own server. OTHERWISE IS NOT DIFFERENT THAN WALLET OS SATOSHI.
reply
For a long term, I may rather run a real LN node than this tbh. Considering the fact that i may still stuck with fedimint even after self hosting.
reply
Quit lying you stupid fuck.
  1. You still have seed words and storage stored locally on the device
  2. The app store apps still exist
  3. The apps are still available on GitHub
  4. It's on the start9 app store
  5. The source code still exists
  6. It's still self custody at the end of the day
You can sit there and continue lying, not knowing what the fuck you're talking about, or you can go do something productive for society.
I won't hold my breath on the latter.
reply
100 sats \ 9 replies \ @javier 28 Apr
I don't want to agitate anybody, but would you please explain if this is possible:
  1. Deploy your own server.
  2. Restore the wallet you created with app.mutinywallet.com in your own server.
  3. Restore the channels in your own server.
Have you tried it? Where is the documentation regarding this?
reply
Yes, just backup the state file and then import it when you set up your own server.
reply
Would you mind provide a link to the documentation? Also, have you thought about storing the channel backup in a cookie or in cloud storage just in case the user don't make a backup on time in case of your server suddenly failing?
reply
It's in your browsers storage, that's where the local backup comes from. It's also remotely stored as well, encrypted.
But when you're self hosting, it's your storage now. So it needs to fill it with your data which is what the state file is for.
reply
Thanks, back to my original question, what would be the procedure to restore the wallet and the channels that you created with app.mutinywallet.com in your own server?
reply
Settings -> emergency toolkit -> save state
Then setup your server and do the import state option.
just backup the state file and then import it when you set up your own server.
I am not opening channel. I am only using fedimint. So self hosting won't make any difference.
reply
Lying? Let me know what you gonna say to mutiny users when the domain mutinywallet.com (where they are running their instance) will get seized.
NOT YOUR DOMAIN = NOT YOUR SERVER
deleted by author
reply
deleted by author
reply