-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fee charged but no new channel created #843
Comments
Because it costs money to open a lightning channel. We communicate this twice when receiving lightning will result in an on chain fee. |
I didn't see any warning of having to open a channel. AND it did NOT create any lightning channel for me. I had 2 channels before and still after receiving. |
If you can provide logs we can see what happened, otherwise we can only guess |
How do I get LOGS? I'm not a dev so I probably won't because to know how to get them without instructions. |
It is in Settings > Emergency kit > Download logs, once you have it, just drag and drop it here |
Thanks, looks like infact you did not receive a channel from the LSP, seems like potentially a bug on their side for wanting to charge you for the channel when you did not need one. Opened a PR that could be a fix for the issue on our side: |
Thank you for submitting. I'll keep watching! |
I make very SMALL amounts for profit with my transfers using Lightning so the $5.34 fee is large to me. |
Sorry about that, we should fedimint support available to the public soon-ish and that'll never have channel fees |
Well, at least the fee wasn't huge. But I'm scared of MutinyWallet now. The only reason I'm here is I maxed out Alby using Zeus wallet. I barely understand these channel maintenance lightning topics; so Mutiny shows me my channels clearer and at least I know if I'll get charged. lol |
Should I just move on from here @benthecarman ? I should expect the fee coming back, right? |
Now, same day. None of my transfers are showing up and now I don't have the funds in my transactions list or my BALANCE! Looks like this Mutiny is a ship I'm being pulled down with? |
You may just need to restore from seed, sounds like you opened a new wallet |
Invoice on the Unpaid one. lnbc1201550n1pj6a5lypp557mgw4n6swl9k27lsp8q58kk5e2ja9fgma8sl5zs38dvfq92wg6sd2j2pshjmt9de6zqun9vejhyetwvdjn5grrvg6x2cehvfnz6vtzvcej6dr9v4nz6wf5x9sj6ve5vvmx2wt9vcungc3c9cs9g6rfwvs8qcted4jkuapq2ay5cnpqgefy2326g5syjn3qt984253q2aq5cnz92skzqcmgv43kkgr0dcs9ymmzdafkzarnyp5kvgr5dpjjqmr0vd4jqampwvs8xatrvdjhxumxw4kzugzfwss8w6tvdssxyefqw4hxcmmrddjkggpgveskjmpfyp6kumr9wdejq7t0w5sxx6r9v96zqmmjyp3kzmnrv4kzqatwd9kxzar9wfskcmre9ccqz2yxqr06gsp5tfut46vnf88asctax35tnmwpu5cdy07mrnrm3pmyaw4780dhuvsq9qyyssqdk9n6mmuzcks0vr3wk0557kw648fuktjsjcg5thd8qxkdsuj3amxvlj6s22qegvwty7dtl3a8afu8ercs2dkagn95egxl8zrcwupg2gqvrr67y |
This is a payment to robo sats, it is a hodl invoice where the payment doesn't settle immediately |
grrr, but it deducted from my balance on MutinyWallet and DIDN'T PAY the invoice. After I get my funds out I'm off this platform |
The funds came back into my wallet now? hmmm |
You should read how robo sats works, this is how it works with every lightning wallet |
Now it says I have 128,863 SATS OUTBOUND and 1092 SATS in reserve |
I loaded $11 more into account to fix the OUTBOUND sats lie |
self-custodial lightning has a lot of caveats that are different than custodial lightning, you can read our FAQ here |
I did the math so that's good I needed to send 120672 Sats and I know it holds 1% in reserve |
You also need to be able the on chain fees if the channel were to close. Being able to spend your exact balance isn't really feasible in lightning |
How do I understand the balance that I need to have for closing the channel? It's not displayed in the OUT and INbound Lightning Channels view? |
I sent this information to the LSP to look into it further and what happened in regards to the channel and fee. |
I was charged a $5.34 FEE when transferring SATS in from Strike app. WHY?

~$5.34 USD
Payment Hash cc932913e5382565fa01c149edcba848a1cc4909e93d80d8861b8a1dd7465bc6
The text was updated successfully, but these errors were encountered: