Coinbase jumped on the 402 bandwagon... yay!
When I talk to people about Cashu they usually ask me: "Why do we need Cashu? We got Bitcoin and Lightning". I used to tell them that Cashu offers a great alternative to custodial Lightning, but with better privacy. While this remains true, my answer today is that Cashu enables new use cases (or simplifies them drastically) where Lightning and Bitcoin struggle.
One example are Zaps. NIP-61 Zaps offer a very similar experience and value proposition as NIP-57 Zaps do, but require only a fraction of the implementation overhead.
The second example (and inspiration for this post) is HTTP 402. With Cashu, we can streamline payments for requested ressources into a single request. Because Cashu is a bearer asset the whole flow is pretty stateless. It is stupid simple to implement this. While it is definitely possible to make 402 work with other "assets", using Bitcoin / Cashu makes it a breez.
This is my favourite thing about Cashu.
When I talk to people about Cashu they usually ask me: "Why do we need Cashu? We got Bitcoin and Lightning". I used to tell them that Cashu offers a great alternative to custodial Lightning, but with better privacy. While this remains true, my answer today is that Cashu enables new use cases (or simplifies them drastically) where Lightning and Bitcoin struggle.
One example are Zaps. NIP-61 Zaps offer a very similar experience and value proposition as NIP-57 Zaps do, but require only a fraction of the implementation overhead.
The second example (and inspiration for this post) is HTTP 402. With Cashu, we can streamline payments for requested ressources into a single request. Because Cashu is a bearer asset the whole flow is pretty stateless. It is stupid simple to implement this. While it is definitely possible to make 402 work with other "assets", using Bitcoin / Cashu makes it a breez.
This is my favourite thing about Cashu.
106β€οΈ14π€3π2π«1
