pull down to refresh
21 sats \ 5 replies \ @justin_shocknet 29 Sep \ parent \ on: Building Lightswap — Why I Decided We Need to Build a Lightning Wallet builders
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.
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