Any client is just 2-3 subtle bugs away from doing that and then it's just matter of someone noticing.

I think my preference is that the wallet creates a dedicated sats account that can only be used for zapping and is somewhat limited in max sats. And once in a while it would notify me to refill it.

Then the potential "total stolen amount" would be limited while the experience would still be top notch.

Reply to this note

Please Login to reply.

Discussion

I don’t think people should be storing significant amounts of sats in these custodial wallets to begin with.

Exactly. You wouldn’t leave your house with your entire savings account in your back pocket. Be smart, only use these kind of wallets for your zapping around money.

True, same can be say about one tap zap. Just how urgently do you need to zap someone that that extra click to send is a burden? πŸ€·πŸ»β€β™‚οΈ

You can’t do seamless client side zap splits without it. You would have to open N invoices externally and pay each one. Noone would do this.

I would rather you do sort of a @Damus gift card (like Amazon gift card) that can be reloaded with sats with your own wallet and then zapped away. That could make it easier and safe.

That’s not really any different than preloading an Alby wallet from your node.

And the problem with going exclusive crypto, as there are no guarantees nor regulations for the the companies responsibilities, and by the time they do offer security and regulations, the difference between fiat and crypto will be insignificant.

Then whether build back better is serving the purpose or a liability, well.