pull down to refresh
False. We don't have control either, and can't read the user's secrets - that's the point of running the node in a TEE. All node code is open-source, auditable, and bit-for-bit reproducible, and clients verify the enclave's remote attestation before connecting.
Educate yourself.
Is totally useless if your server /domain goes bust... Yes you cannot control user's node details, traffic etc, but for the user is totally useless that control if they do not control the hardware and domain where the node is running.
This is exactly the same situation as was Mutiny.
Not your hardware... not your node.
You still haven't named a single thing that could go wrong with our architecture.
EXACTLY that architecture that I depend of your infrastructure to be able to make payments... that's not self-custody, is just renting hardware.
It doesn't serve me if I can recover the funds by force closing a channel. I need that wallet to MAKE payments.
Call it whatever you want but don't bullshit me that is "self-custody", when is not.
I have nothing against custodial wallets, but at least don't lie the users. Just say it clearly what it is, not bullshit lies trying to fool noobs.
Self-custody means only you hold the keys and no one else can spend your money, which is exactly what Lexe provides.
If you want to make payments from your Lexe wallet without using any of Lexe's hardware, then you can run a LDK node on your own machine using your Lexe seedphrase and channel state and make payments that way.
You can continue to waste everyone's time keyboard warrioring for your own revisionist definition of "self-custody" while also completely failing to understand how Lexe works, but that doesn't change what everyone else understands "self-custody" to mean.
please stop call it "self-custodial" when is running on a remote server that user have no control.