<oembed><type>rich</type><version>1.0</version><title>Derek Ross wrote</title><author_name>Derek Ross (npub18a…tp424)</author_name><author_url>https://nostr.now/npub18ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqctp424</author_url><provider_name>njump</provider_name><provider_url>https://nostr.now</provider_url><html>Today I learned a lot about Lightning. For example, if you have very old LND channels, it&#39;s possible that they won&#39;t be of the ANCHOR channel type. These cannot be CPFP fee bumped. It&#39;s also possible that older CLN channels are this way too. I have 43 channels and 4 of them are of the STATIC_REMOTE_KEY type. Those 4, if they get force closed, cannot be fee bumped.&#xA;&#xA;My bad luck left me a channel with a lot of sats on my end, of a channel that was remotely opened to me and a non ANCHOR  channel. Essentially the worst combination.&#xA;&#xA;This left me with a pending transaction of 1 sat/vbyte. It could take 6 months for the mempool to almost clear again. But, there&#39;s also a chance that my transaction never gets through too. Especially with the upcoming bull run next year, we just don&#39;t know what it&#39;s going to be like.&#xA;&#xA;So, what does a Nostrich do in this situation. Well, for starters, I got annoyed and freaked out. I then spent two days trying to resolve this. &#xA;&#xA;And then I paid F2Pool 147K sats for them to include my transaction in an upcoming block. That may seem like a lot, but I had 6.5M sats on the line here. That&#39;s an incredible amount of Bitcoin to me. This gives me peace of mind.&#xA;&#xA;To prevent this from happening, I&#39;m probably going to close the other 3 channels that I have open that are not ANCHOR channels so that this does not happen again. I&#39;ll reopen what I can when I can.&#xA;&#xA;At least I can now go to bed a happy Nostrich.&#xA;&#xA;Goodnight!</html></oembed>