LLMs are so well tuned for optimizing the lighting pathfinding problem. Give them a dataset and tell them to optimize a parameter and they go ham.
Big things ahead for the LDK pathfinder and lighting payment success rates.
Matt Corallo
matt@bitcoin.ninja
npub185h9...wrdp
10th known contributor to Bitcoin Core. Now Full-Time Open-Source Bitcoin+Lightning Projects at Spiral (Part of Block).
This idea that lightning nodes, by default, store every single invoice or offer you generate over RPC is insane. There’s no reason to bloat the DB and expose users to DoS risk if they generate invoices automatically, the damn things can be stateless and additional metadata you need can be stored in the invoice and retrieved on payment, rather than stored.
I fully do not understand the desire of lightning people to build protocols to “buy a channel”. No one has ever wanted to “buy a channel”, they want to buy reliable HTLC delivery. That might imply multiple channels, splicing, and probably implies just-in-time channels, but it definitely doesn’t imply just buying a channel and calling it a day.