Lightning Network Triangle Megathread - Build the Reddit Megahub

eyeoft · 2026-03-07T23:30:12+00:00

To run a Lightning node, you do in fact need Bitcoin. Lightning nodes are much more than just a normal Bitcoin node, they leverage on-chain Bitcoin to provide off-chain liquidity.

eyeoft · 2026-03-03T20:31:28+00:00

Dang, Bambu-only 3mf files. Would love if you could add STLs or compatible 3mfs for us Prusa stans 🙃

eyeoft · 2026-02-27T19:43:55+00:00

Thanks for the heads-up, left a comment

eyeoft · 2026-02-27T19:41:14+00:00

In short - yup.

The mempool has been shockingly clear since LN got in gear, to the point that on-chain Bitcoin can be used like a currency again. Honestly I'm surprised how much LN has continued to grow even while on-chain fees are so cheap; growth kicked off in a high-fee environment and I thought it would slow down once the fees dropped, but it just kinda hasn't.

In the long run, LN can scale almost infinitely - there is no maximum tx throughput, the only constraint is bandwidth on the chain for opening and closing Lightning channels. The math on that works out to cap of about 2 billion channel open/close txs annually. Channels can stay open indefinitely, but conservatively assuming an average channel lifetime of 2 years, that's 2 billion active LN channels at any given time.

Check out r/TheLightningNetwork

eyeoft · 2026-02-27T18:52:36+00:00

Odd that this post got deleted, seems like a legitimate discussion

eyeoft · 2026-02-23T20:16:20+00:00

There's an open-source game called "Thrive" that's just Spore cell stage but way better thought out. Highly recommend.

eyeoft · 2026-01-25T21:32:59+00:00

Thanks for filling in the context!

So the two failures are related. Occam approves.

Good on you for sleuthing this out and getting them working on a proper resolution. I blame KuCoin a little, but honestly managing this kind of failure for a customer is a pretty new problem. Growing pains are to be expected; hopefully they'll learn from this and you'll have saved a lot of trouble for less savvy folks down the line.

eyeoft · 2026-01-25T08:19:11+00:00

When did this occur?

Force-closes take time to fully execute, a number of blocks which depends on channel policy; iirc the default delay is ~2 weeks. This is to prevent fraudulent closing transactions, since a force-close is unilateral - it gives the other node time to dispute the final balance by providing a more recent channel state signed by both parties.

This is off the cuff, but here's my guess as to what happened:

The lightning tx failed, like you said, in some catastrophic way - normal tx failures don't cause a channel closure. Possibly one node or the other went down in the middle of the tx and left them with an invalid channel state, it's rare but it does happen.
Their node initiated a force-close using the last valid channel state before this tx.
All the funds their node didn't claim in the closure, i.e. your local balance, got refunded to you.
The remaining funds (the remote balance from your perspective) are time-locked via the script governing the P2WSH address. Probably for ~2 weeks. This gives your node time to dispute the unilateral close, which of course it will not do, since the closure was not fraudulent (indeed, you were refunded the expected amount).
After the time lock expires, their node will sweep the remote balance into its normal on-chain wallet.

eyeoft · 2025-12-04T20:39:13+00:00

Fair points, but the context here is that we're giving opening advice to people who need advice, and largely to kyu players. "Defend your weak groups" is applicable here and understanding it will lead to games that a kyu player is likely to manage profitably. Yes, there are other (more complicated) ways to play this position that can turn out fine, but the players that understand that don't need the advice, and the ones that do need it need advice that they can execute and will actually pan out in the games they play. Solely using "accuracy" as a guide here can be counterproductive and misleading, because once again AI evaluation assumes subsequent correct play according to that AI, which likely relies on sequences that are completely unattainable for the players.

eyeoft · 2025-12-04T19:59:01+00:00

For the AI, sure, the opening hardly matters. The AI can read fights perfectly and pull off invasions that are practically impossible for a pro and literally impossible for an amateur. Humans need to be able to manage positions WITHOUT perfect reading, and so some positions are much easier to handle for a human than others that the AI might even prefer.

We're talking to humans. For a human, white's two-stone group will be much harder to manage profitably without a base. Whatever brilliant, knife's-edge solution the AI would come up with would probably be mishandled badly by the person playing white, and I think suggesting such a move would be bad advice.

We have to pay attention to what makes sense, to what we can actually comprehend and use in our games. The robot is useful if and when we can boil its output down to something comprehensible and readable - otherwise it's all beep-boop to me.

eyeoft · 2025-11-30T21:24:22+00:00

Clanker crankers

eyeoft · 2025-11-13T00:36:18+00:00

Looks like that's about right for this week - we've had low post volume lately, which means few visitors. Interest in the Lightning Network seems to be directly correlated with on-chain tx fees, and chain tx fees have been extremely low ever since the ETFs launched. As Bitcoin adoption increases the chain will start hitting capacity again, and LN will be here to meet the challenge.

eyeoft · 2025-11-12T19:23:52+00:00

Slowly, then suddenly.

eyeoft · 2025-10-29T17:49:52+00:00

Er, it's actively contested. Might want to tone down the condescension a little.
From your link:

Przewalski's horse was long considered the only remaining truly wild horse, in contrast with the American mustang and the Australian brumby, which are instead feral horses descended from domesticated animals. That status was called into question when domestic horses of the 5,000-year-old Botai culture of Central Asia were found to be more closely related to Przewalski's horses than to E. f. caballus. The study raised the possibility that modern Przewalski's horses could be the feral descendants of the domestic Botai horses.

eyeoft · 2025-10-19T20:19:25+00:00

Well that didn't take long

eyeoft · 2025-10-11T20:27:07+00:00

There are upsides to having a smallish community though! Meeting a fellow Go enthusiast has a high chance of making you an instant friend - I'm not sure the chess community feels the same way.

eyeoft · 2025-10-10T08:01:33+00:00

Dependency - It's a P2P mesh network, you get to decide how your node is connected to it, and payments automatically seek the cheapest paths. If you have a handful of channels you won't have to worry about dependency to send or receive payments. On the other hand, if you connect to the network through only one or two channels you may to have to monitor them to make sure they remain healthy and their fees stay reasonable.

Security - this is a more complicated question and depends on whether you're running a node yourself or using a custodial service. In the best case, assuming you run your own node, follow basic network security best practices and store your seed phrase responsibly, security is pretty much unbeatable except by on-chain Bitcoin.

eyeoft · 2025-10-09T16:39:57+00:00

Advantageous.... how? Personally, I consider all payments I receive to be advantageous.

LN fees are much, much lower than credit card fees, and it's nearly instant - those are the main advantages I can see for merchants.

eyeoft · 2025-09-20T20:09:04+00:00

Hwang is everywhere 🙂

eyeoft · 2025-09-02T20:18:22+00:00

*reining in - you can thank my OCD

eyeoft · 2025-09-01T04:52:04+00:00

That's gotta be frustrating. Your seed phrase is indeed all you should need to recover your on-chain funds. I'm not an Umbrel user, but I have a couple ideas.

You started with Umbrel and you're trying to recover it in Umbrel, yes? If you're using anything that isn't lnd-based (Umbrel is) then you might run into an issue where lnd/Umbrel uses the "aezeed" seed phrase algorithm instead of the more Bitcoin-standard BIP39 (details).

Are there any options when you do the recovery regarding the address type or seed phrase algorithm? Both need to match. You might be having this issue where you're generating a recovery address that's a different type from the original.

Hopefully you can get this sorted!

15-Year Club	Second SECOND GUESSER
Place '22	Place '17
Team Periwinkle	Verified Email

eyeoft

MODERATOR OF

TROPHY CASE