A while back I set up a self-hosted mutiny wallet instance using Start9. Never used it for lightning channels, but joined the freedom one mint for ecash. Since then I’ve been receiving small amounts from lightning into the wallet ecash. All smooth until trying recently to send those sats out to another lightning wallet via lightning invoice. Getting unknown error after hitting send. Tried restoring the wallet with seed words, but that didn’t help fix the error. The amount of sats is not enough to transfer to lightning via channel creation mechanism. Any help on this would be appreciated!
131 sats \ 1 reply \ @Wumbo 12 Sep
Have you tried:
Any ecash balance you have in the app should be transferred out as well. The easiest place to go is the Fedi app. If you join the same federation in the Fedi app that your Mutiny Wallet app belongs to, transfers should have low fees. The self-hosted version of Mutiny is still able to be a fedimint wallet if that's your desire.
I understand you are self hosting but transferring out might be path of least resistance.
Mutiny is shutting down. (Just in case you miss the news)
reply
Thanks. I did hear news of announcement. I should mention I also tried sending out to Fedi, albeit to a different mint, doing so however also resulted in the same unknown error.
Using the transferring out to lightning mechanism is really my last resort for me, as it means I would have to deposit quite a few more sats into ecash balance to reach the minimum amount (100k) which I don’t want to risk. Especially with this unknown error state I’m experiencing when trying to send.
reply
Rugged.
Why would you self-host an ECash interface for someone elses mint? If you have a start9 just run a real node.
reply
Not sure what you’re talking about. Who says I’m not running a “real node”. I’ve self-hosted Mutiny Wallet, and used it exclusively for the integrated ecash interface for small amounts.
reply
Not sure what you’re talking about
Mutiny is a PWA that runs a node on your phone, that's all your serving from the Start9... you're not actually using the Start9 as a node in this context... your using it to host an ECash interface to someone elses mint which is why you got rugged
reply
Friend. You’re not telling me anything I don’t already know. And if I got rugged it’s because freedom one is rugging, not because I self hosted Mutiny and used ecash with it. ✌️
reply
Instead of trying to open a lightning channel maybe try sending the funds from the mint to a lightning node that already has inbound liquidity.
reply
Lol. The latter is what I’ve attempted. The former is what I haven’t attempted. I guess you haven’t read my post…
reply
I had read your post. There is no need to get angry with me. I don't run the freedom one mint.
The amount of sats is not enough to transfer to lightning via channel creation mechanism.
I understood that you were trying to send to a LSP and have the channel opening fees deducted.
Then it looks like you have been rugged. So much for "ecash, the future of (custodial) bitcoin".
reply
Not angry really. Very small amount. Not trying to open new channel with LSP, just to transfer to existing LN wallet with inbound liquidity. Lol so much for the ecash narrative.
Hopefully this gets boosted for visibility. I have 123 sats in my SN wallet right now, I plan to have the same when activity on this post dies.
reply
According to what you say, you have 123 sats, could it be that the minimum limit to send is much higher? Could you take a screenshot of the error and thus have more visibility of your problem? A picture says more than a thousand words?
reply
123 sats in my SN wallet. Much more than that in mutiny eSATS. Approx. 7k. Tried various send amounts ranging from 1k through 7k. No difference in error msg I receive (unknown error).
What I was implying with bringing up amount in my SN wallet was that no matter how many sats I receive for this post, I intend to give them all back to the community. I’m not here to try and gain back the eSATS I’ve apparently been robbed of. I’m here to discover what the root cause of issue is (technical bug or rugged) and raise awareness of either.
reply