Challenges of Building a Non-Custodial Lightning App \ stacker news ~meta

pull down to refresh

Challenges of Building a Non-Custodial Lightning App github.com/stackernews/sn-talks/tree/develop/btcpp-berlin-2025

3469 sats \ 25 comments \ @ek 3 Oct meta

Here are the slides that I used during my presentation at lightning++ today

view all related items

160 sats \ 7 replies \ @SimpleStacker 3 Oct

Man, this slide makes me realize that what we need is industry standards for wallet interconnectivity

169 sats \ 2 replies \ @ek OP 3 Oct

Protocols like LNURL or NWC are standards but users don’t understand them, they would rather click their wallet and go from there. We showed protocols before and it was confusing.

50 sats \ 1 reply \ @SimpleStacker 3 Oct

Ah, yeah good point. I haven't used that many different wallets, but the process of getting the NWC string seems like it might be different for each wallet too.

148 sats \ 0 replies \ @ek OP 3 Oct

Yes, and would be nice if the user didn’t have to open the wallet and find that setting themselves, but SN opens the wallet and the user only needs to approve or deny (#1245549)

257 sats \ 1 reply \ @justin_shocknet 3 Oct

... missing the slide where everyone eventually converges on CLINK

17 sats \ 0 replies \ @ealvar26 4 Oct

Lol that's brilliant m8

30 sats \ 1 reply \ @ek OP 3 Oct

But if you mean something like „Login with Apple“ but for wallets, you might be interested in #1245549 (though quite technical)

We will also not show all wallets immediately but give some beginner options first like Coinos, Ecash or Spark

13 sats \ 0 replies \ @DarthCoin 3 Oct

We will also not show all wallets immediately but give some beginner options first like Coinos, Ecash or Spark

In other words "we are not custodial" but we throw the dead cat to the others. Pushing users to go to other custodial crap (LOL even Spark) is NOT a solution.