exactly ? I’m not going to accept the payment until i redeem it as a lightning payment to my node, since it could be a bullshit token. So it’s just a slower payment method now? Who is benefiting from this? Users get slower payments, seller has to do extra work. Still uses lightning at the end of the day to verify. Please make it make sense.

Reply to this note

Please Login to reply.

Discussion

The only way I can think of justifying it, is if there is a Huuuge mint, and it issues and redeems for aaaaall users. With minimal need to go back to Lightning.

But then… that’s just a mildly less centralized table. 🤷‍♂️

I haven’t been able to figure out the good use case for it either. Maybe because of offline payments?? That’s the only argument I can see. But you can’t verify it. I’d rather take cash and convert that to sats.

yeah lightning wouldn’t work in some places where visa works, like in an airplane with no wifi.

so this is where ecash works better, but you could rugpull the airline right when you get back online unless they redeem before you

Exactly. It’s outside my risk tolerance.

Everyone risk tolerance.

Actually you can verify it. By combining DLEQ proofs and locking scripts you can verify a token yourself (no request to the mint needed). You can aggregate payments and then swap out to Lightning whenever you like

You can verify they are real. But you can’t verify that they exist, have not been double spent, or the mint closed while you are holding the verified token.

You can verify that they are real, that the mint that you trust has issued them, and that they are not double spent.

I’ll give you the last one though. If you don’t trust your mint in the slightest, Cashu might not be for you.

can you show me code that does this? I find that hard to believe. At the end of the day unless the sats are in my lightning channel i’m calling bs.

Sure! Here are the specs:

DLEQ proofs: https://github.com/cashubtc/nuts/blob/main/12.md

P2PK: https://github.com/cashubtc/nuts/blob/main/11.md

Here is a very basic Cashu 402 controller (it does not have P2PK and DLEQ yet, but that’s only a couple lines of code I will add soon): https://github.com/cashubtc/npubcash-server/blob/v2/packages/server/src/controller/username.ts

However this is only beneficial if you keep Cashu (at least for a while). You can verify every payment immediately, aggregate them and then swap out from time to time

I am respect and salute to people who can create something like this . It took hard work 👏

Sounds way more complicated than just using lightning.

But it’s not. With Cashu a payment can be part of a single web request. With Lightning you need plenty (return invoice and identifier, check invoice payment state, return resource after payment).

I downloaded cashu the other day both on android and iOS , then I delete it . I can’t remember why , .. oh now I remembered it . Something with Mint token

It’s because ecash or Cashew is not decentralized network , E cash depends on central mint or federation issued the token, while lightning wallet is decentralized so no one control the bitcoin .

Hmm , Lightning send actual Bitcoin over the network , while E cash just send tokens issued by the issuer .

You really need to trust the issuer or else you get screwed .