pull down to refresh
174 sats \ 9 replies \ @ek 28 Sep \ on: Building Lightswap — Why I Decided We Need to Build a Lightning Wallet builders
Non-custodial? Custodial? Trustodial?
We’re exploring a non-custodial setup with managed node operations.
Users hold their own keys. The underlying infrastructure (like Greenlight) simply handles the node management and reliability side.
In short: you control your funds, we make it work smoothly behind the scenes.
reply
That'd be just another trustodial mobile wallet, greenlight doesn't solve trust or issues of mobile offline-ness since there's still bi-direction with the remote signer (phone)... it's just a gimmick to scam the regulator... not a solution.
You're also still going to need integrations to other apps/services to get utility out of it... and that utility isn't going to improve by being just another trustodial wallet that can't help people actually earn sats.
I do like the idea of a language based interface, I've tinkered with it myself as that's really the killer app of "AI" in my view #1017929... but time is scarce...
Would be interested to collaborate if you back the wallet with Lightning.Pub, our wallet client is already bundled into a proto. A language interface over its RPC would be a great pairing given its powers.
reply
Thanks for the feedback @justin_shocknet, you make some interesting points in your linked posts. I'm never heard of Lightning.pub so will check it out in detail. I'm going to ponder on some of your comments. In an ideal world what stack would a mobile wallet use?
reply
Lighting is inherently different than the chain in that Lightning has an interactivity requirement to coordinate stuff that happens above the chain... so the ideal mobile lightning wallet is really a mobile client that connects to a remote server (node), just like your email client on your phone connects to a mail server.
Lightning.Pub is my striving for the ideal: Light, Efficient, Shareable, Easy.
Perhaps someone will execute better than us at some point, but afaik no one else is even trying. Maybe LNbits and BTCPay are in some ways, but I don't think they're as focused on powering clients-everywhere as we are.
Outside of the Lightning stack, we use Ionic Framework for the wallet since it's allows for a single code-base to be used across mobile OS's and WebApps while still providing access to mobile native API's.
reply
And great job on building lightning.pub, whilst I haven't looked into it in detail, I can see it's no small job
reply
ty, don't hesitate to reach out with any more questions or to sync up.
reply
Got it. And in the ideal scenario the lightning.pub is run by the user? so effectively you're connecting to your 'home server'?
reply
Correct. You could use it to provide a custodial service, but the idea is that it will enable trust and custody to be localized to the extreme... family and small business nodes.
It's also light enough (neutrino based lnd, nodejs, sqlite) to do greenlight-ish things with generic container/VPS hosting, but like greenlight/lexe/voltage etc there's still trust in the host even if it's "non-custodial".
Since it uses nostr for identity and comms there's also some social graph implications we're working towards, users may connect to a pub based on who it's administrator is.
reply
Nice. I'll check it out later this week.
reply