Non-custodial Lightning security for serious balances. Off-node keys + full validation = a compromised node can’t steal funds Open source Rust SDK. https://xitter.cf/t.co/uyM2m1tBs7

Joined September 2020
Validating Lightning Signer retweeted
Replying to @evankaloudis
@VLSProject can come in handy
1
1
2
42
Validating Lightning Signer retweeted
Great description of where @VLSProject can help a noderunner: AMA is rocking and rolling, come join us! stacker.news/items/1584228
5
6
238
Validating Lightning Signer retweeted
AMA with @VLSProject happening now! Join us for discussion of using a signer and policies to mitigate the risks of running a lightning node. stacker.news/items/1584228
2
2
225
Validating Lightning Signer retweeted
Starting in 1 hour! Come join us on Stacker News for an AMA with the crew from @VLSProject
4
5
189
Validating Lightning Signer retweeted
📢 Stacker News AMA Announcement: @VLSProject! The team from the Validating Lightning Signer project will be joining us to talk lightning security and using a dedicated signer with lightning. 🗓️ Tuesday, 29 September 2026 ⏰ 10AM Texas time, 1500 UTC 📍 stacker.news/~AMA
1
4
2
9
590
Validating Lightning Signer retweeted
Attackers aren't going away. Understand the vectors.
Lightning funds have been lost to race conditions, fee gaps, and stale state. None of those attacks broke cryptography. Understanding why is the best reason to spend twenty minutes on our site.
1
2
51
Validating Lightning Signer retweeted
.@VLSProject validates: on-chain sweeps, cooperative closes to attacker addresses and arbitrary outbound payments. It's the control policies so even if your LN node is attacked policies you set still control your capital. In most cases it would have completely eliminated the results of these attacks on BTCPayServer Wen LND implementation?
2
4
338
Validating Lightning Signer retweeted
UX is the most talked-about Lightning adoption bottleneck. But there is another one that gets less attention: operators with real money do not yet trust the security model enough to commit real balances. Both need solving.
1
3
5
196
Validating Lightning Signer retweeted
Excited to be speaking at @btcplusplus Nairobi this June. I’ll be talking about Lightning node security and how @VLSProject uses policy-based signing to help protect funds incase of a node compromise. Looking forward to connecting with builders in Nairobi. 🇰🇪⚡
JUST IN 🦒: Sulaiman Aminu Barkindo (@SulaimanAminuB2) of BTrust — Contributing to Validating Lightning Signer (VLS) to speak at bitcoin++ Nairobi, open source edtion this coming June 17-19, 2026 ~~Don't Trust Your Node: Policy-Based Signing for Secure Lightning Infrastructure~~ Join us 👉 btcpp.dev/nairobi#tickets
5
8
33
2,360
Validating Lightning Signer retweeted
JUST IN 🦒: Sulaiman Aminu Barkindo (@SulaimanAminuB2) of BTrust — Contributing to Validating Lightning Signer (VLS) to speak at bitcoin++ Nairobi, open source edtion this coming June 17-19, 2026 ~~Don't Trust Your Node: Policy-Based Signing for Secure Lightning Infrastructure~~ Join us 👉 btcpp.dev/nairobi#tickets
12
1
36
3,475
Validating Lightning Signer retweeted
Previously a grantee in 2019, 2020, and 2021, open-source Lightning legend Zmnscpxj (not a nym, his parents are computers) is back for number four. Z Man, as he’s known to us, will be building out multi-signature support for Lightning Network nodes via the @VLSProject.
🤖 Made with AI
7
10
1
38
2,702
Validating Lightning Signer retweeted
Most Lightning setups still assume the node can be trusted with keys. It can’t. VLS is built around a different assumption: the node can be compromised, and funds should still be protected.
2
3
118
Great article by @VLSProject on Lightning security. Thanks for the shoutout! Check it out here: vls.tech/posts/lightning-sec…
2
4
319
Validating Lightning Signer retweeted
@SulaimanAminuB2 is driving the @VLSProject to mainnet readiness, integrating secure persistence, fuzz testing, dual funding, and splicing support while improving entropy security and enterprise‑scale validation. His long‑term focus on security and enclave deployments will make VLS production‑ready for non‑custodial Lightning operators.
1
4
20
452
Validating Lightning Signer retweeted
Replying to @SulaimanAminuB2
@SulaimanAminuB2, software engineer and Btrust grantee, joins the #BtrustDeveloperDay lineup with a hands-on technical workshop. Sulaiman is currently contributing to the @VLSProject, an initiative dedicated to enhancing the security and reliability of the Bitcoin Lightning Network. His work focuses on improving HTLC security and developing disaster recovery mechanisms to ensure performance and integrity across Bitcoin’s Layer 2 scaling solutions. Through his efforts on VLS, Sulaiman is building tools that help developers run more secure and efficient Lightning nodes, while strengthening the foundations of Bitcoin’s decentralized payment infrastructure. His session will guide participants through practical steps for setting up, securing, and automating Lightning nodes, combining technical depth with an emphasis on privacy and resilience. RSVP now to secure your spot: clooza.com/events/BTRUSTDEVE…
1
11
30
564
Validating Lightning Signer retweeted
Most Lightning wallets blur the line on custody. In the latest blog from @VLSproject, @Blockstream’s Greenlight stands out as the model that lets builders offer Lightning access through apps or wallets without giving up control. ⚡️ Node ops in the cloud, signing on-device
3
5
33
4,510
Validating Lightning Signer retweeted
A validating signer is the only way to combine hosted nodes with real self-custody.
1
3
18
3,970
Validating Lightning Signer retweeted
A Lightning wallet is only really self-custodial if: 1. The node runs on your device or 2. You connect to your own node or 3. You're using VLS If it’s using the provider’s node, your keys don’t protect you. The provider's node can tell your wallet to do anything.
1
4
12
788
Validating Lightning Signer retweeted
A wallet that blind-signs but calls itself “non-custodial” is like a bank claiming it’s non-custodial because they don’t know your online banking password.
4
10
330