nostr login should be the standard. All apps and websites hopefully cave eventually to this reality.

Your example of cashu manages the stamping demonstrates my idea. Your app needs a monetary layer, and it would already be built in. You don't need to "support" cashu, you just need a standard plugin. If the user uses Fedi, your stamp is paid and the message is sent. A sat is a sat.

You would be able to divert dev resources away from all the changes to the cashu protocol, and just maintain the payment protocol standard. It would free the user to select something they like better. There are users who would not use your product *because* you chose cashu.

Down the road, if fedi "wins out" and cashu becomes marginalized, you would have to do some restructuring.

I like standards and modularization. Its freedom increasing.

Reply to this note

Please Login to reply.

Discussion

Fedi sats as message stamps are far inferior to Cashu sats because they are more complex. We speculate that users will prefer to store larger amounts of sats in self-hosted Lightning Network wallets rather than in Fedi. Once users have accumulated enough Cashu sats, they can open a Lightning Network channel.

I agree that cashu is better, and a good choice for your use case.

And maybe cashu would be the "standard" payment processor in my super app, for the reasons you stated.

Self-custodial lightning is ideal for the spending wallet. Cashu solves the uncle jim, the offline, and the not enough sats to justify the fees problems.