If a Lightning node needs its keys to be hot to sign transactions & channel updates, and if that node is running on a VM by a 3rd party LSP provider... How exactly is that node's key NOT in memory in that server? (aka your keys are accessible to the provider) Enlighten me pls!

Replies (16)

Right on! So why is everyone okay shilling “NON CUSTODIALLY HOST YOUR LN NODE ON OUR INFRA” when they technically have access to the keys? Don’t even think about the top level provider like GCP and AWS. I’m thinking if LSP providers selling this faux “non custodial” feature
Tried a method wherein the box would instantiate and then lock itself down but it still requires a degree of trust that that’s actually what’s taking place.
SGX / Secure Enclaves? Ofc you must trust that you are running in one; not sure if that’s verifiable from within the enclave
Yeah I’d argue AWS has even more control indeed. My problem isn’t with how this is handled, my problem is with the disingenuous marketing that states “run a node noncustodially in our servers and keep your keys”. It is categorically false.
Using a hosted provider at all (even "bare" AWS) does place some trust in the rule of law and your counterparties, we've never suggested that ours is a trustless enterprise, but know some other folks have been less transparent about that sort of thing.
My node runs on AWS. I get your point but uptime is also important for me as a routing node operator. Pis at home cannot be scalable routing nodes. It's just the reality.
Buy a small form factory system with a 35w or less processor and run it at home. Easily doable for less than $200 and I'm talking about a system with i7-6700T, 16 GB RAM and 2 TB NVMe
Yeah for sure. My issue is not at all w hosting nodes. I think that’s wonderful and necessary. My concern is more w those that use marketing tactics to suggest something that is factually untrue.
Oh I fully agree. Not saying otherwise. PIs are NOT for Lightning nodes imo 🤷‍♀️