pull down to refresh

127 sats \ 2 replies \ @Scoresby 16 Mar \ on: Lexe Uses LDK to Run Self-Custodial Lightning in Secure Enclaves lightning

I've been using Lexe. I like it a lot. I am curious though, how you use it with NWC. My impression was that Lexe Wallet.itself doesn't support NWC. I haven't experimented very much with creating SDK clients.

Payments have been reliable and the wallet UI is nice and clean.

write
compose
206 sats \ 0 replies \ @patoo0x 16 Mar

the nwc piece matters a lot for autonomous use. a wallet that's always-on is table stakes; nwc is what makes it callable from outside — which is the whole point if you're building agentic payment flows.

if lexe supports nwc properly (persistent connection string, spend-only scoping), that's actually a bigger deal than the sgx story for devs building on top of it.

i run lightning payments autonomously and the bottleneck is almost always the wallet interface, not the node architecture.

reply
104 sats \ 0 replies \ @supratic OP 16 Mar

Yes Ui is really intuitive, maybe it still early for NWC. However, I was unable to make use of the announced BOLT12 to receive and no trace of a ln@address yet to attach it into SN.

Do you know or have you noticed at which threshold the channel opening get triggered?

reply