Well, that certainly sounds like an interesting premise.

I've operated a Lightning node for a couple years now, and I'm not sold on ecash yet. As far as anonymity goes, I always thought that running Lightning over Tor was enough - is this not the case?

I can imagine that, if I want to give friends access to operate through my system, I'll need to have some standard for keeping track of how much each person holds. It seems that this is the use-case that ecash aims to solve, but it certainly seems like a complicated way to go about it. Is there something I'm missing? 

 I am designing this first and foremost as a backend component to my Lightning payment system. Each user will have their own #safebox instance stored on relays, versus a wallet stored in a database system. It solves a big problem for me, in that I can provide a custodial lightning payment service, but give the use independent control if they want to move the safebox elsewhere n 

 If you add this to a Linux machine, each user account automatically gets their own wallet. No extra effort required. 

 Neat, I like the simplicity of that approach. So the "wallet" here is an ecash wallet, which can send and receive tokens to a cooperative Lightning node in exchange for a lightning transfer of equal value? 

 You don’t even need a Lightning node. The mint takes care of all of that. Works with multiple mints. 

 Right,  but in my case I *want* a Lightning node. How does that work, I suppose I would need to run a mint myself? 

 Sure, if you want to run your own mint. That’s what I do, as well have my own relay. The point is that it is completely flexible. 

 Neat! There's a lot here, I'd have to read up on everything else it does but this seems to be a good option for the use case I'm looking for. Thanks for fielding the questions.