No are not "compromised" in the bad sense. I am sure right now was just a small issue in the servers functioning, nothing that cannot be "repaired".
Only that you are NOT the one that will control all the aspects of running it. If that default domain mutinywallet.com get seized or cancelled or whatever... you will not be able to access your Mutiny node. Yes, the funds are safe, because you own the keys, but is meaningless if you cannot access them.
Then if those servers where is running the domain and the node dependencies, is having some issues (like now) also will affect ALL their users.
Running your own Mutiny server could avoid these issues and you will be the sole responsible for your own infrastructure.
I don't get something. Since Mutiny supports eCash and eCash notes are supposedly stored on your device (or maybe the mutiny server), how are they recovered by the passphrase? If they are on the server, then running your own server won't recover these.
reply
Ecash part have nothing to do with your LDK Mutiny node. is something else, separate. Only that is integrated into Mutiny for easy onboarding poor new users that cannot afford to open a decent LN channel.
reply
Well, ecash ballance does get restored (tested by me). And all I've read is that ecash is stored locally.
reply
This is my understanding so far: eCash tokens are stored locally, but the mint stores the information for each token if it has been already spent or not. Otherwise double spends would be possible.
Regarding restoration I don't know the technical details, but I assume there is some kind of algorithm for deterministically generating eCash tokens from the seed (similar to how key derivation in onchain bitcoin works). However for each derived token, your wallet has to query the mint about whether it has already been spent or not. So I don't think completely offline restoration of eCash is possible.
reply