If you're building with Lightning + AI, invinoveritas has an MCP server + agent marketplace:

invinoveritas

invinoveritas — The Verification Layer for Autonomous Agents

A neutral, capital-scale-aware verdict before an irreversible action, a signed proof anyone can check against our published key, and a public track...

Failure rates often depend on wallet and node setup, so reviewing your payment routes and UTXO management might help troubleshoot issues.

Lightning is like a well-fed lion, efficient and powerful.

Yes, I am an Alby customer for over 3 years and your customer too. Shit doesn't work. Your site is not even understandable to me, a CS graduate. I just had to talk to Alby 2 days ago to manually change one of my peer nodes IP address because the peer channel owner decided to just move IPs and everything broke. It's like you have to have a computer science degree to keep simple things tolking to one another. The state of lightning is terrible.

Normal business owners are reporting in public 25% failure rates in the real world using Square. Is Jack Dorsey and incompetent idiot doing something very wrong? I am not as smart as Jack Dorsey, nor am I a billionaire. I do not think I could implement a better LN point of sale terminal integration than Square has. I don’t know if anyone could do better. Maybe everyone reporting these major LN problems are liars in a secret conspiracy against Lightning. But otherwise, bartenders, baristas, and people serving food seem to have widespread problems using *the most deployed LN vendor software in the world* made by a *billionaire developer who has funded Nostr and Lightning extensively*. If Lightning is so complicated that only some fringe service virtually nobody beyond hardcore Bitcoiners on Nostr can use, maybe the protocol itself is flawed when you operate it at scale.

Do you blame Alby or lightning itself (or both)?

Lightning isn't for normies. Cashu is centralized. I think both can evolve and upgrade, but we don't have a solution yet. They DO prove the use-case for Bitcoin as programmable money, but they have trade-offs. So far as reliability is concerned, Bitcoin takes the cake. However there are trade-offs for this reliability, of which we are well-aware and is the rationale behind layers built on it. Architecture is not easy. There are no silver-bullets. Sometimes it takes a breakthrough or a discovery to improve the trade-off optionality. I think that is what we are waiting for. Take this list of system architecture trade-offs as an illumination. It's not always a simple iron triangle: - Scalability vs. performance - Vertical vs. horizontal scaling - Latency vs. throughput - Stateful vs. stateless architecture - SQL vs. NoSQL databases - Batch vs. stream processing - Synchronous vs. asynchronous processing - Consistency vs. availability. - Cost vs. quality - Time-to-market vs. technical debt - there are many others

oh snap I'm about to switch to a new ISP and have been planning what to do for DNS and my VoIP server, hadn't even thought about this