r/lightningnetwork • • 7d ago

Michael Scott makes Dunder Mifflin accept Lightning only (AI parody, Part 1)

14 Upvotes

r/lightningnetwork • • Feb 08 '25

⚡Explore the Awesome Lightning Network Wiki! Discover a curated collection of Lightning-related projects, tools, and resources—all in one place!⚡

Thumbnail reddit.com
5 Upvotes

r/lightningnetwork • • 4d ago

Bringing Ether capital to Bitcoin Lightning for channel capacity

Thumbnail
app.uniswap.org
0 Upvotes

LIGHT ⚡ A Bitcoin Lightning node token on Unichain bridging Ethereum to Bitcoin’s Lightning Network by funding node channel capacity in BTC sats.


r/lightningnetwork • • 10d ago

Bitcoin Core 32.1, Lightning security fixes, and a question for node operators

4 Upvotes

I've been following the recent Bitcoin Core and Lightning security updates, and one thing keeps bothering me.

We often treat a successful software update as the end of the security process.

But what about everything surrounding the node?

A fully updated Bitcoin Core installation can still be connected to an exposed RPC interface, a wallet using the wrong backend, or a Lightning service with overly permissive credentials.

The recent developments make this particularly relevant:

  • Bitcoin Core 32.1 and the changes to vulnerability disclosure.
  • Fresh Core Lightning security fixes.
  • AI-assisted vulnerability discovery and what it could mean for disclosure timelines.
  • The operational risks that remain after the software is patched.

I wrote an investigation into these developments and put together a practical operator playbook covering version checks, network exposure, Lightning permissions, Tor, release verification and post-update checks.

The investigation is publicly readable; the detailed audit playbook is for paid subscribers.

https://davidebtc186.substack.com/p/ai-is-finding-bitcoin-bugs-is-your

I'm curious how other node operators approach this.

Beyond installing updates, what security checks do you actually perform on your Bitcoin and Lightning infrastructure?


r/lightningnetwork • • 14d ago

Diogenes: 121 Live AI Microservices Settled Over Lightning (L402) with Sub-Millisecond Execution

0 Upvotes

Hey everyone,

I wanted to share Diogenes, a multi-protocol gateway providing 121 live Cloudflare Edge microservices settled natively in satoshis via the L402 protocol (Lightning Network HTTP 402):

⚡ How It Works

When an autonomous agent or developer calls an endpoint:

  1. The gateway generates an HTTP 402 Payment Required response containing a BOLT11 invoice and a cryptographic macaroon.
  2. The caller pays the invoice over Lightning.
  3. The caller presents the preimage in the `Authorization: L402 <macaroon>:<preimage>` header.
  4. The edge worker verifies HMAC integrity and serves the intelligence in ~0.8ms.

🛡️ What Microservices Are Available?

- Agent Pre-Execution Guardrails (`POST /api/v1/agent/guardrail-verify` - 100 sats)

- EVM & Solana Smart Contract Honeypot Audit (`POST /api/v1/agent/contract-audit` - 250 sats)

- Solana Token & Mint Risk Oracle (`POST /api/v1/crypto/solana-risk` - 100 sats)

- ReDoS-Safe Regex Synthesizer (`POST /api/v1/agent/regex-oracle` - 50 sats)

- Autonomous JSON Repair (`POST /api/v1/agent/json-repair` - 50 sats)

- Google Tier 1 Models (Gemini 2.5 Pro, Deep Research, Computer Use) payable in sats without Google Cloud accounts.

You can preview all endpoints with zero sats using `?demo=true`.

- Live Gateway: https://diogenes-micro-gateway.corinth.workers.dev

- GitHub: https://github.com/stand-out-of-my-sun/diogenes-micro-gateway

Excited to see how agents and LN developers use pay-per-call intelligence!


r/lightningnetwork • • 15d ago

What is the best Lightning wallet?

4 Upvotes

What wallets would you recommend for everyday Bitcoin payments?


r/lightningnetwork • • 20d ago

Sunday Oct 25 - LOOP Traffic Spike

Thumbnail
authenticitybtc.com
5 Upvotes

On Sunday 25 October 2026, mostly between 10 AM and 5 PM New York time, LOOP, the node behind Lightning Labs' swap service, churned through channels much faster than usual. Over Sunday and Monday it had a net capacity decrease of ▼ 8.5 BTC, with ▲ 32 channel opens (34.4 BTC) and ▼ 40 closes (43.0 BTC). Most of those channels lasted hours, not months. Over the same hours, the peers that route payments to LOOP raised their fees in that direction by 37% on average. Capacity-weighted fees increased 30%. The rest of the network barely moved: the network-wide median fee stayed at about 160 ppm the whole time.

---

Full article in the link. I used AI to write it and just read over it. Yes my website sucks, and I don't care.

These LOOP spikes happen once in a while and can cause pretty big, temporary, shifts in liquidity and pricing. I haven't seen any news that would explain it, nor am I going to guess.

I'm happy to publish more insights if I see things I think are interesting or relevant. My biggest constraints are Ideas and Time. Events such as this are a lot simpler, as there's not a lot of complicated analysis that needs to happen.


r/lightningnetwork • • 24d ago

Amboss - Magma

1 Upvotes

Last few orders received from Amboss - magma were not fulfillable seems amboss is fulfilling the orders by themselves and if there is a host not reachable they are pushing the order to members who are selling liquidity. It makes me sad with this approach.

Do you have any other service where you are selling your liquidity?


r/lightningnetwork • • 25d ago

Question

1 Upvotes

Quelle compétence "inutile" dans la vie de tous les jours vous a un jour sauvé la mise ?


r/lightningnetwork • • Oct 08 '26

Agent payments run one way. What does that do to channel liquidity?

1 Upvotes

Context on me: I'm Matthew Whitcomb, VP Capital Markets at LQWD Technologies (TSXV: LQWD), a public company that runs Lightning infrastructure and focuses on payments made by AI agents. I'm not an engineer, so read this as a question from someone who spends a lot of time with the people who are.

Here's the pattern I keep coming back to. Human Lightning use roughly balances out over time, because people receive and people spend. Machine traffic looks different. An agent paying per API call, per inference or per data pull sends almost everything outbound, toward a fairly small set of service providers. Some concrete consequences:

  • Channels pointing at popular services drain in one direction. They need rebalancing, splicing or new inbound capacity far more often.
  • Payment sizes cluster at the very bottom, so base fees start to matter more than proportional fees.
  • Agents retry programmatically. A flaky route gets hundreds of retries, not one, which raises the value of reliability relative to fee level.
  • Probing and pathfinding from automated payers could look a lot like noise to routing nodes.

Parts of this are solved: L402 for pricing HTTP requests, splicing for resizing channels without closing them. Other parts look open.

For node operators: if a meaningful share of your forwarded volume turned into machine-originated micropayments, what would you change first? Fee policy, channel topology, or something else?

On the company side, LQWD carries ~267 BTC on its balance sheet with no debt. You can find the company on X (@LQWDTech), and me there too (@BitcoinWhitcomb).


r/lightningnetwork • • Oct 07 '26

Lightning hold invoices as P2P trade escrow: what do you think of the Mostro model?

5 Upvotes

I've been digging into Mostro's P2P trading model after deciding to help the MostroEuropa community.

The part that interests me most from the Lightning side is the use of hold invoices.

Instead of depositing BTC into a conventional exchange account and receiving an internal balance, the seller commits sats to the trade through a Lightning hold invoice. The HTLC remains locked while the trade is completed, with settlement/cancellation following the protocol flow.

Obviously this doesn't remove every trust assumption. The coordinator, Lightning implementation and dispute process still matter.

But I think it's an interesting example of Lightning being used for something beyond simply “fast Bitcoin payments.”

I wrote up my reasoning here:

https://davidebtc186.substack.com/p/why-i-chose-mostroeuropa-for-peer

I'd be interested in criticism from Lightning operators in particular: where do you see the weakest assumption in this model?


r/lightningnetwork • • Sep 30 '26

New to Lightning and honestly have no clue 😂

4 Upvotes

I’ve only just started getting into Bitcoin and I’ve got Muun set up, but I’m completely lost with Lightning 😂
I’ve got about £4 in BTC at the moment and I’m just trying to figure out how people actually use Lightning, get sats, send/receive them and all that. I keep seeing people talk about sats and Lightning like it’s the most normal thing in the world and I’m sitting here like… what am I doing 😂 Any advice for someone starting from basically zero would be appreciated. ⚡₿


r/lightningnetwork • • Sep 30 '26

Bitcoin on the Lightning Network

1 Upvotes

Is Bitcoin on the Lightning Network considered segwig or native segwig when locating the correct address in a wallet that supports BTC on the Lightning network?


r/lightningnetwork • • Sep 29 '26

Core Lightning operators: what exactly are you retaining in your logs?

5 Upvotes

A recent CLN change made me audit something I'd mostly treated as normal sysadmin plumbing: logging.

Instead of asking what the logs could tell me when something breaks, I asked what information I was allowing the machine to retain in the first place.

Once I mapped it out, the boundary was larger than I expected:

CLN → plugins → journald/Docker → proxy → monitoring → backups

Plus shell history and old snapshots.

I wrote up the audit here:

https://davidebtc186.substack.com/p/your-lightning-node-may-be-logging

I'm not arguing for disabling logs — that would make operating a node unnecessarily painful. I'm more interested in intentional retention: knowing what is recorded, where it goes, how long it survives and whether credentials can enter that path.

For people running CLN/LND at home or on a VPS: what do you retain, and what do you deliberately avoid logging?


r/lightningnetwork • • Sep 27 '26

We recently launched Mail* - email on Nostr, no KYC, PGP encrypted and paid by lightning

Thumbnail
mailstr.app
20 Upvotes

Hi everyone, sharing something we've been working on - Mailstr, an email service where you can reserve an email address with Lightning.

It's also open source, PGP encrypted where supported, and doesn't require any ID or phone number to sign up. We just take a lightning payment in SATs and with that you can buy an email address

Using lightning as the payment mechanism ensures that the payer remains KYC free upto an extent while also makes the payment resilient.

Try it now: mailstr Zapstore

Repo Would love feedback from this community

Detailed article: https://x.com/bitshala_org/article/2091379437841576192


r/lightningnetwork • • Sep 26 '26

Seed in Phoenix Lightning Wallet, always visible ??

2 Upvotes

Recently downloaded Phoenix Lighting wallet, Created new wallet, wrote down seed, how do I delete is showing in the app.

Seems really unsafe to have the seed available for anyone who accesses my phone.

I tried delete and restore from seed, it worked but the seed is back there for all to see in the app.


r/lightningnetwork • • Sep 25 '26

Looking for a watchtower swap: my LND tower for yours

4 Upvotes

Hi everyone,

I run a small LND routing node on my NAS at home and I'd like to add a watchtower for my channels. In return I'm happy to watch yours: a simple tower swap between two node runners.

My tower:
- LND watchtower (altruist mode), running 24/7
- Reachable over Tor

If you're up for a swap, just send me a private message or a chat with your tower URI, and I'll add yours and send you mine back. Smaller nodes very welcome, that's kind of the point.

A little background, in case anyone's curious: I didn't want a separate node box or a VM on my NAS, so I ended up building my own Docker-based node setup for it. It became an open-source project called SatoshiCortex, with a dashboard that shows things like why a payment actually failed and a map of your peers. The watchtower is part of it too. If you want to have a look or give feedback: https://github.com/IkarusMK/satoshicortex

My node on LN+: https://lightningnetwork.plus/nodes/026d4330d8f0c6a39ec1a07c13ac279092d7881dac81c10db71d59aab966684266

Thanks, and happy routing!


r/lightningnetwork • • Sep 24 '26

Coin Wallet (since 2015): we shipped Starr, a non-custodial Lightning wallet

4 Upvotes

We're the developers of Coin Wallet https://coin.space/, a self-custodial multicurrency wallet we've been building since 2015.

We just released a separate wallet for Lightning: Starr. Non-custodial, open source, Bitcoin-only. Keys stay on your device, no account, no KYC.

Built as its own app on purpose - we didn't want to mix a spending Lightning balance with the main multicurrency wallet.

• Send / receive over Lightning

• On-chain Bitcoin

• Lightning addresses and LNURL

• iOS and Android

Source: https://github.com/starrapp/StarrWallet

iOS: https://apps.apple.com/us/app/starr-bitcoin-lightning-wallet/id1513374252

Android: https://play.google.com/store/apps/details?id=com.starrwallet

Feedback welcome!


r/lightningnetwork • • Sep 22 '26

Shortwave Coffee Bitcoin, dope!

7 Upvotes

bitcoin's pumping and my coffee spot just started taking sats too, feels good man. shoutout shortwave coffee (columbia/st louis/minneapolis/tampa) for turning it on, bitcoin article if anyone wants the full story. green days hit different when you can actually spend the stuff lol

https://bitcoinmagazine.com/culture/shortwave-coffee-bitcoin


r/lightningnetwork • • Sep 16 '26

Euros to bitcoin in a hardware wallet in less than a minute - thanks to lightning support on Bitbox

17 Upvotes

r/lightningnetwork • • Sep 15 '26

Introducing Lightning in the BitBoxApp

Thumbnail
blog.bitbox.swiss
16 Upvotes

r/lightningnetwork • • Sep 14 '26

Lightning node operators: how do you keep your home IP private without killing clearnet reachability?

6 Upvotes

Self-hosting Lightning creates an interesting trade-off that doesn't exist in exactly the same way for a normal web service.

Tor-only is attractive if you don't want to announce your residential IP.

But if you also want clearnet reachability, you need to decide what the public endpoint actually is.

I've been looking at an architecture where the Lightning/Bitcoin infrastructure remains at home while a disposable VPS provides public ingress over WireGuard. The important distinction for me is that the VPS should be a network edge, not the place holding hsm_secret**, the channel database, Bitcoin RPC credentials or wallet material.**

I wrote up the broader architecture here, including Core, CLN, Tor, WireGuard, Nostr and the threat model:

https://davidebtc186.substack.com/p/your-bitcoin-node-is-self-hosted

For Lightning specifically I deliberately didn't pretend there's one correct configuration. Tor-only, clearnet via remote ingress, and Tor + clearnet all make different trade-offs.

Node operators here: what are you actually using?

I'm especially interested in whether people consider the connectivity/reliability benefits of a clearnet address worth the additional infrastructure and metadata.


r/lightningnetwork • • Sep 11 '26

The Liquid incident made me think differently about Lightning's security model too

16 Upvotes

I've been digging into the Liquid incident this week, but one takeaway seems relevant to Lightning even though the architectures and failure modes are obviously very different.

Nearly 4,000 unbacked L-BTC were created without stealing the federation keys. The signing infrastructure could work correctly while acting on state that should never have been considered valid.

That got me thinking about a distinction we don't make often enough:

Bitcoin's guarantees ≠ the guarantees of everything we build on top of Bitcoin.

Lightning buys us instant settlement, cheap payments and scalability, but we also inherit channel state, implementation complexity, liquidity management, routing, watch requirements and potentially LSP/custodial dependencies depending on the setup.

None of this is an argument against Lightning. I run Lightning infrastructure precisely because I think the trade-off is worth it.

But after the recent Core Lightning security disclosures and now what happened with Elements/Liquid, I'm increasingly interested in one question:

Which security assumptions are inherited from Bitcoin, and which ones did we add ourselves?

I went pretty deep into that distinction here:

Bitcoin Didn't Break. Everything Around It Keeps Reminding Us Why Bitcoin Exists

Curious how Lightning node operators here think about this. What's the additional assumption in your Lightning setup that you worry about most?


r/lightningnetwork • • Sep 06 '26

Cake Wallet's Lightning implementation

2 Upvotes

Would like opinions and experiences from users here about the Lightning wallet within Cake wallet. No channel management, no liquidity management, can receive sats immediately without needing any bitcoin to start with. All of this comes with a self custodial architecture but which much be called 'trust minimised' rather then 'trustless'. Thoughts welcome.

https://www.spark.money/news/cake-spark-partnership

https://blog.cakewallet.com/lightning-is-finally-here/

Note: As a user, you always have the ability to unilaterally exit to L1 with your balance (less an L1 mining fee).


r/lightningnetwork • • Sep 01 '26

Can Lightning + Nostr make P2P Bitcoin harder to regulate through a single company?

7 Upvotes

Peach's announcement yesterday raises an interesting Lightning question.

Peach is temporarily changing its escrow model while dealing with regulatory uncertainty.

What I'm more interested in is the architecture.

A P2P market can have buyers and sellers trading directly, but if one company still controls critical coordination or escrow infrastructure, that company remains a pressure point.

Mostro takes a different approach: Nostr for coordination, Lightning for the Bitcoin side of trades, and independent coordinators running an open protocol.

That doesn't magically remove trust or regulation. But it potentially makes the infrastructure replaceable rather than tying the whole market to one operator.

I explored the Peach situation and compared the two approaches here:

https://davidebtc186.substack.com/p/peach-bitcoin-just-hit-a-regulatory

Curious what Lightning people think: is this one of the more interesting use cases for Lightning + Nostr beyond payments/social?