welp. lost my first funds dude to a force close somehow in nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg. I'm am le sad. I won't stop using it though. those boys are doing some sick shit.
Shouldn't be lost lost, just needs to be swept back after. Click on the channel close item for more info on it.
With rising fees, it's even more important that you check your lightning mobile nodes more often in order to update channel fees.
Further, if you were the channel opener (instead of the LSP opening a just in time channel to you), then you may not be able to take advantage of your full balance since part of your funds need to be available to close the channel eventually. We'll update the UI next week to reflect that. If you're getting low on funds (<100k sats) and you opened the channel by swapping from on chain funds to LN, you may run into instant payment failures.
Mempool is coming down again. Weirdly enough that has something to do with it. We'll try to push out a release next week to partially address this edge case.
nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg
Please fix this, it's important.
It is not a complete solution for all security problems, but it is an important measure.
The protection of users and their data should be a top priority.
Fixed, thanks for the report.
Maybe there was a connection issue between your node and the LSP? Restart, wait a few seconds, then try again? Otherwise, submitting logs to our GitHub could help us investigate.
Ah, was trying to zap this and was wondering why the payment wasn't showing up. Zeus user 😂😂
gn nostr:npub1xnf02f60r9v0e5kty33a404dm79zr7z2eepyrk5gsq3m7pwvsz2sazlpr5 users
Make sure to check your zaplocker instance before going to bed so Zeus can take his 50% cut
We are. Tbd on next LDK release.
https://github.com/lightningdevkit/rust-lightning/issues/2336
And yes, if/when the fees go down, they would go out. We may have to update a lot of things to account for this new scenario.
That sounds accurate and consistent with what we're seeing right now. This wouldn't be an issue if the LSP opened the channel to you.
nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg is yallz LSP having trouble ? Getting failed route for all my zaps or any sends i try.
No, odds are it's related to a smaller balance you might have and potential on chain fees dominating your next potential send.
Sending logs to our GitHub would help verify this but if it sounds like your balance is low and/or across multiple channels then that's probably it.
Freedom to get rekt.
If you want to potentially pay outrageous on chain fees due to a stuck zap to nostr:npub1xnf02f60r9v0e5kty33a404dm79zr7z2eepyrk5gsq3m7pwvsz2sazlpr5 - you can go right ahead. It's in the admin section of the settings.
Invoices and lightning addresses were always allowed, it was just zaps, which are typically low in value and are done without the user knowing they're potentially paying a hodl invoice. This is also wasteful to the network from a locked htlc perspective.
This was never a hypothetical situation, there has been many instances of this happening to our users since Zeus Pay, and with on chain fees being really high, is not worth making small payments that get stuck. But if you want to do that now, glhf.
Well then you'll need people to actually zap you that isn't yourself.
PRs welcomed.
Nuances.
nostr:note14dp7rj2pg2q4zu78pmhdjvgdan5pkpemxgqvlrftzupffp9l5w2qhvar0c
Sounds like their pipeline trick worked on you.
"pipeline" more like "shut up quit asking us for it"