pull down to refresh
Agreed. Much like my other old project CLBOSS, however, any deployment that includes VLS with CLN can only be improved compared to just CLN out-of-the-box.
Even if you end up just running VLS on the same machine as the node software (very much NOT our recommended setup), if you do something like run them as separate users and restricting the VLS user and completely disabling its password (which you should also do to CLN BTW if you can arrange it), you can still get a little more security simply from the additional isolation.
At the moment, no. But we are in working with some folks. Once anything materializes, we will announce.
I do know of maybe two or three large Lightning operators / services who are interested in possibly integrating VLS, but I do not know if they would be willing to let me share their names :P you would just have to trust me that we do have a few potential users asking about us.
Greenlight is somewhat unique in that their service inherently depends on VLS being actually a thing (they want you to run a VLS on your hardware, while they run the CLN node on their server rack).
This pretty makes sense. They are giving the user the power of self custody of their keys while taking care of the technicality and running of the node.
Our hope is that it becomes a standard that everyone running a node will use, so that everyone can benefit from the increased security.
But, in terms of a path to wider adoption, we do think it would start with LSPs, professional node runners and routing nodes, really anyone with a lot of sats to protect.
For smaller balances, until the wallets make the UX seamless, I could see how people won't bother. Much like how many people do not take self-custody of their L1 bitcoin today.