Still alpha, but ShockWallet is already the best Lightning wallet as a daily driver by far imo
Super fast and reliable, its not a mobile node so no waiting to boot or graph syncs that cause failures
Using Nostr real-time sync is a handy flex too, one wallet on desktop phone ๐ค
Login to reply
Replies (13)
Is this custodial?
Connects to a remote node over Nostr, can optionally start custodial and upgrade when you have enough sats or set one up from scratch in 2 minutes
Demo from Nashville.... Going from 0 to a shared Lightning Node in 2 minutes
Paste one line into an old laptop or small VPS, and connect anyone you know to it instantly
Nostr based accounts completely eliminate the fussy networking
Automatic channels from top LSP's
View quoted note →
I think it would be really cool if the Lightning.Pub accounting system (for users using shockwallet) was on top of a cashu mint and not only a pure LN node (neutrino). In this case you could have both the nostr real-time sync and connection to the node (instead of having to manage VPNs, Tor, etc...) and privacy for each user wrt the node operator, right? And maybe this could enable a "private cashu mint" where only whitelisted npubs could connect (family, friends, etc...).
Apologies for the newb question:
Do i need to have this Ubuntu computer on 24/7 for this to work properly?
Could this also be done with Phoenixd? Maybe with a layer on top of Phoenixd to also work over nostr?
Yea we built Lightning.Pub around LND but in a way it shouldn't be too difficult to create adapters for other backends
Justin likes cashu like Kamala likes press conferences
Cashu/ECash is a bad design choice for this usecase imo, it makes tradeoffs incompatible with fluid mass-adoptable UX because its just layering the management of a new shitcoin as opposed to direct RPC access
Save for enterprise-scale environments, Pub isn't any less private either as it uses ephemeral keys that are blind children not tied to a given identity. A user could have one or many, rotate them, etc. Also with friends/family nodes nodes the anonymity set is so low that becomes the common limiting factor... whitelisting keys would also negate any privacy benefits
If however you are already running a mint, it could conceivably serve as a backend for Pub... while we built on a single implementation to focus on security (LND) we did so in a way that adapters should be relatively simply to implement
Most of the benefits come from it being always-on 24x7 but it won't hurt if it goes down from time to time
It'll run on Windows/Mac too but would be a manual installation
I personally recommend an old laptop with clean *buntu install, the built-in battery makes it much less likely the node gets corrupted. Since it uses neutrino a 4GB of RAM clunker with ~20GB of free disk should be adequate (would suggest an SSD at least though)
I should caveat that we have NOT automated watchtower setup yet, so something to consider if you'll be offline regularly
I might not have the ability to properly view each pro and con since I am not that technical into cashu and LN low level details and for sure you make some good points, but I still have some questions/doubts:
- Aren't people connecting with shockwallet to a Lightning.Pub node effectively using a custodial service? More trusted for sure if they use a friend or family one, but still custodial right? So in this case isn't using a cashu mint as a base adding only benefits? You still need to trust the node not to "rug pull" the LN liquidity right? Which is the "same" with a cashu mint or am I missing something? (A part from the added technical layer obviously)
- So if I am understanding right, under the hood you basically have "multiple keys for each user" so it would be problematic to add whitelisting (please "explain like I am 5" if not ๐
) and it will negate the benefits of it. Then again the anonymity set is usually low in uncle jim nodes, so almost perfect privacy of cashu mints is not that perfect and not that almost ๐คฃ .
So basically you say that the Lightning.Pub implementation is actually more private (for this kind of use case) and simpler (less technical layers)?
Hope I am understanding right.
If you're the node operator then its self-custodial, with the option to add custodial guests. The goal is to let people who prefer a custodial solution keep that as close as possible. Most people share a house/fridge/car with people already, and they'll share a node / channel too.
There's no benefit in Cashu as it's the same scenario with either... if you run your own mint then its self custody, else it's custodial.
ECash is worse UX because there's fragile gateway and settlement layer between it and real Lightning payments, and on the client side you're reintroducing bearer shitcoins thus making the worst combination of trade-offs: a custodial solution that still requires key management.
It's not that Pub is more private, it's just not less, the overall point is that you shouldn't use either for privacy as both are limited by the nodes anonset. Since a node operator has countless ways to deanonymize activity, you simply shouldn't use a custodian you don't trust and ECash doesn't make a custodian you don't trust anymore trustworthy. ECash's privacy benefits would only come at bank or government level scale which is even more dangerous because of how much oversight those mints would have into the flows of the Lightning network... this is why it's so important we make custodians small... ECash is for governments not families.
