I agree with @DarthCoin and I want to expand on what he said:

This is an absolutely awesome way to make a user friendly Bitcoin wallet. I love the idea.

BUT. You need to find a way to abstract this stuff away from users altogether. Automatically assign them to different layers depending on their balance. I know this is easier said than done, because of the differences in disclosures on the different layers. But I think more effort should be put into it.

I strongly believe that "ecash" should be thought of in the same way we think of the database layer of an app. Typical apps do not start off by confusing users with sentences like: "This app uses SQLite. Please be aware that SQLite is not meant to be used for heavy industrial data solutions. Please be aware your data could be lost using this database."

Fuck that. Developers abstract these sorts of details away, and at the moment, Bitcoin developers are doing an absolute garbage job with the PR surrounding "ecash". It sounds like a shitcoin. People are confused.

Sure, we developer types get it. We love ecash, just like we love SQLite or mySQL. But FFS, keep this shit out of the public eye!

See my comment thread on this subject from a few months back: #557913

I want an app with all the features of Blitz, but with a UI like Zues. Actually, fuck that. Even Zues is silly by not finding a way to abstract LN/on-chain concepts from users. CashApp or Strike might be doing it best. Just find a way to be like CashApp, but add self-custody features for users with high balances.

But whatever, the main point I want my post here to get across is that ecash should be thought of like a DB layer. And we should only be talking about it in highly technical Bitcoin communities and podcasts. Don't confuse the non-techies.