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

Replies (1)

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.
โ†‘