We're rethinking RTL's UX and exploring AI-assisted analysis for node ops. Before designing anything, we want to know how you actually run your node. Please let us know via this 2-min survey below 👇

Release candidates for lnd v0.20.5-beta.rc1 and v0.21.4-beta.rc1 are now available. Both are maintenance releases with bug fixes. If you run lnd in a test or staging environment, please try them out and let us know how it goes. github.com/lightningnetwork/… github.com/lightningnetwork/…

⚡ RTL v0.15.12 is out! 🔒 Login lockout: now expires, no X-Forwarded-For bypass (proxy? set trustedProxies) 🔑 Settings API can't re-point credentials 💰 LND: open a channel with the whole wallet balance 🧾 Eclair: paged invoices, honest failed opens github.com/Ride-The-Lightnin…

Latest Strikes is (finally) out! In this issue: - @BtcpayServer vuln - @ZeusLN attack - LND Vulnerability disclosure @lightning @realtbast - @lightningdevkit release - @RTL_App release - @arkade_os and @secondhq LN-related updates - new channel jamming proposal & more! 👇

Running LND in production means knowing when to upgrade. The new published policy gives you that clarity. Lightning Labs maintains the two most recent release lines, and both get security fixes. A line reaches end of life when the second major release after it ships, so support tracks releases, not a calendar date. Once a line reaches end of life, it gets no further fixes. Run the latest minor of a maintained line to keep getting LND security fixes. As of today, the latest minors of maintained lines are v0.21.2 and v0.20.3. For more details: security.lightning.engineeri…

A self-custodial Bitcoin Lightning ⚡️ wallet inside Telegram. Proof of concept on signet, built on Lightning Labs' Wavelength SDK. The full Wavelength〰️ daemon runs in the browser via WASM, so the keys never leave your device. No app install, no account. Test coins only! Try it: t.me/wavewalletsignetbot Build your own solutions: wavelength.lightning.enginee… Feedback and bug reports very welcome.

I think the Lizard People have surrendered to Bitcoin Core, which, if true, means that we have an extremely powerful tool in popular open source software, categorically. It's too hard to slip in corruption with all the world's most competent eyeballs watching. The Lizards are now trying to centralize keys. We need to make self custody as realistic as possible and not let them reach whatever tipping point of keys they calculated. Notice, that while the details differ, they are running they same playbook as they did with centralizing gold. Gold failed because it's various properties made it vulnerable to capture by central bankers. Gold was too expensive/burdensome/risky to self-custody. Notice, again, the narratives emerging from the CC heist. "Screw it, self-custody is too hard, I'm moving to an exchange." "They did everything right." "Death of self-custody." Each hack/heist encourages the average Bitcoiner to conclude that self-custody isn't worth the risk. That their odds are better with a "well-trusted" institution holding their keys instead. That an institution is the easy button. If you were a lizard, you'd attempt to introduce critical bugs in specialized HWWs (and their related software stacks) to encourage this migration to institutions. Each bot repeating that Core is too hard to learn, that something like Yeti Cold is too tedious, advances the Lizard's goal of key centralization. Call to action: make self-custody as realistic as possible. Reject specialized HWWs. Take one Saturday to learn how Core actually works, it's just software. Learn how to secure generational wealth, it's not beyond you. And pass the knowledge you learn onto the next pleb. Follow these anons to learn more. @JWWeatherman_ @heavilyarmedc @BenWestgate_ @LibertyMugs @epic_curious

To everyone trying to contribute by finding vulnerabilities in Bitcoin applications, even if you're not an experienced researcher and aren't confident in your findings: learn and practice RESPONSIBLE DISCLOSURE before taking any other action.

There is a critical vulnerability being actively exploited on BTCPay Server, which can result in the loss of funds. Please update your BTCPayServer to 2.4.2 by going to Admin Dashboard -> Server -> Maintenance -> Update & verify the 2.4.2 version string in the footer. If you are unable to update right away, turn off your BTCPay Server to prevent unauthorized access until you can update.

⚡ RTL v0.15.10 is out! 🔒 Credentials kept out of node logs & API responses 🔑 Hardened login validation + server-side auth pinning ⚡ LND alias lookups bounded — no request storms 🧹 Production deps clean at 0 vulns Operators encouraged to update 🙏 github.com/Ride-The-Lightnin…

If the thief has a conscience, they can return my family’s 2.476 BTC to this address: 3M2DTZW9WaXMVYztuJ9s37iQwCzeZTLB27

1/ Block’s engineering and security team found another set of transactions that could be a part of the Coldcard drain. We’re still working to vet these completely, but given the situation, we feel it’s important to share early.

COLDCARD Mk3 Security Advisory If you generated a seed on a Mk3 after firmware 4.0.1, your funds may be at risk. Mk4, Q and Mk5 are not affected based on our early analysis. Read the advisory and migrate carefully: blog.coinkite.com/coldcard-m…

If you have bitcoin residing under a single key that was generated on a Coldcard Mk3 between 2021-2023, and you - did not incorporate dice rolls - do not use a passphrase - do not use multi-sig I would advise moving funds as soon as possible.

Announcing the new L402 site! l402.tech With L402, agents can pay with bitcoin and natively authenticate. No accounts, no intermediaries, no humans involved. Instant, high volume, low fee. The protocol for machine-to-machine commerce on Lightning. Start building the AI economy today. 🤖⚡

I wrote this thread 5 years ago. Since then, Lightning has matured and node management tools have come a long way. I still think running a node is part science, part art. Automation handles a lot, but it still benefits from human judgment. I run mine with both. Maybe that won’t be true in another 5 years. Today, I think it is.

Please take 2-mins to fill up the survey 👇

Hey there, if you're a RTL user, we can really use your feedback to guide the product evolution. Please take 2 mins to fill the survey 👇 Thanks