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.

I've been using Muun to move BTC via the lightning network. I've been having trouble over the past few days. Googling the issue seems to bring up mixed answers. Are there current issue moving BTC via lightning?

Using covenants, one UXTO can be shared by a million users. Any user can leave at any time in a single transaction. Users don't need to be online to receive. Funds never time out. Transaction introspection techniques permit batched exit from the system in a single transaction w/o any pre-signing.

LayerTree is the next step in bringing bitcoin to billions.

Learn more: http://layertree.tech

mostly normies paying with stable coins but somebody is riding the lightning ⚡️ ⚡️

Hi everyone!

I just spun up my new LND standalone node (acermamy-solo-ln). Since it's a completely fresh setup with no open channels yet (0 active channels, fully synced to chain and graph), I am currently invisible to the gossip network.

I am looking for a small inbound channel (e.g., 100k - 200k sats) from an active peer just to break the ice and get my node on the map.

Specs & Network setup:

• Hardware: Dedicated Acer machine (running 24/7)
• Software: LND v0.21.1-beta
• Network: Clearnet IPv6 and Tor active, port 9735 open.

My Node URIs:

Clearnet (IPv6):
02d24c7f204b0a9904410b14c1c95babbafc8cadb956d88b3a5385b4c20a9f98a0@[2a00:1f:fc03:201::2000]:9735

Tor:
02d24c7f204b0a9904410b14c1c95babbafc8cadb956d88b3a5385b4c20a9f98a0@tx5yd44q2emntczokdwsy6ch2mcletmuyskhuub6c5e5fvn43qpdq4id.onion:9735

Any help to kickstart this node is highly appreciated! Thank you, plebs!

Hi everyone!

I just spun up my new Umbrel Lightning node. Since it's a completely fresh setup with no open channels yet, I am currently invisible to the gossip network and cannot register on LightningNetwork.

I am looking for a small inbound channel (e.g., 50k - 100k sats) from an active peer just to break the ice and get my node on the map.

Specs & Network setup:

• Hardware: Umbrel VM on my homlab, Xeon server, ECC memory, NVMe RAID array (Running 24/7).

• Network: 1/1 Gbit symmetric WAN with fixed IP. Port 9735 is open and properly forwarded on my OPNsense firewall.

• Location: Europe / Hungary

My Node URIs (feel free to connect via Clearnet or Tor):

Clearnet:

03a9157cc2f7a36dc482af2d7f3e189f29335fd8cde11d1863d8b07eb3bd8a4d25@zstakacs.eu:9735

Tor:

03a9157cc2f7a36dc482af2d7f3e189f29335fd8cde11d1863d8b07eb3bd8a4d25@epipfc5ljjhpxhknggzwxo4ffal6euv6ampc4vl55me2ylbcf5yk26yd.onion:9735

Once the gossip network synchronizes, I will be hosting a Nostr relay on this infrastructure. Any help to kickstart this node is highly appreciated! Thank you, plebs!

SOLVED - Many thanks SatsFaction!

It’s a live view (time delay, obfuscation, generalization) of Authenticity’s HTLC flow.

Thought I’d share as I think it’s cool and useless, and people might want a view into how active Lightning is.

Leaving this here for anyone interested in a rational overview of BIP110.

Bitcoin, BIP110 and the Burden of Proof | A Reflection on Jack Kruse’s Argument

lightningbazaar.com.au/burden-of-proof/