A web UI for your LND/C-Lightning/Eclair node⚡Devs: @Suheb__ @ShahanaFarooqi⚡UX: @diogorsergio⚡
#Bitcoin
Nostr: npub1yz94p8f8xxg7y9nkjuhlw9a2k6e2279zn6t79gdrs
⚡ RTL v0.15.16 is out!
🍪 Session & CSRF cookies scoped to /rtl, not sent to sibling apps on a shared origin (BTCPay)
🐳 Docker image picks up Alpine's fixed CA bundle (eMudhra)
📦 body-parser patched; prod audit 0
Operators encouraged to update 🙏
https://t.co/epYuOqIvHG
⚡ RTL v0.15.17 is out!
🔑 Login fixes: site-root logins work again, logout clears cookies
🔐 2FA tolerates a server clock up to 30s off
🐳 Docker image on Node 24 LTS
🧾 Label any LND on-chain tx; stable CSV columns
Operators encouraged to update 🙏
https://t.co/W3Cz7WAR3x
⚠️⚠️ All LNbits users should stop their LNbits servers IMMEDIATELY. ⚠️⚠️
Please forward this announcement.
Following a wave of attacks, we have a number of security patches to push. Until then, it's better to err on the side of caution. 🙏
Updates to follow soon.
Wavelength ships with a built-in MCP server. ⚡
One command to add it to your agent's config. 🤖
And like magic, your agent can send and receive bitcoin with Lightning.
Watch the demo.👇
🚨
due to CVE-2026-111943 (eMudhra CA compromise: ⓸㆕), we strongly recommend all lnd/btcd/tapd/litd users to either update to the release binaries below, or re-build their binaries with Go 1.27.3:
* lnd: https://t.co/nASK8lSYdU
* tapd: https://t.co/EgsAOpiqPS
* btcd: https://t.co/5hGvEAI6Mg
* litd: https://t.co/6zhZDkiD1J
Odd one on my Core Lightning node this weekend:
- an unannounced peer opened a channel
- routed a burst of payments through the channel
- spliced
- then forced a close
Looks like a failed exploit attempt. Node was already on v26.06.8, funds are safu
If you run CLN, upgrade now
LND v0.21.4-beta and v0.20.5-beta are out 🚀
Maintenance releases with key bug fixes, incl. one for HTLCs that could be left pending and trigger unnecessary force closes.
All node operators are encouraged to upgrade.
https://t.co/EAV1Gdunix
https://t.co/sP2lqCq92i
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.
https://t.co/ifgcros00L
https://t.co/fP3N7CfOBz
⚡ 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
https://t.co/1JbIRVLkz2
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: https://t.co/MyhQWdv8Ec
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: https://t.co/HCdRWEte5W
Build your own solutions: https://t.co/vjCYpNwdiN
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