Ecash payment request:
- Receiver generates nostr keypair and shows QR code with npub and a set of relays (is there a standard or NIP for this?)
- Sender sends ecash per nostr DM to npub and relays in the QR
Nostr is becoming the native messaging layer of Cashu.
'nprofile' can include relay information
Do you figure this is the way? It should be a new identity for every transaction.
Are we going to move towards a universal payment request which will allow the client itself to figure out which methods are supported and what the best option to use is?
nuts, nuts for everyone 🐿️
Yes, easy. nprofile can encode relay hints. However I would not build on that, but roll our own spec, that can include an amount, memo, etc
All good points
What about using bip32/85 to derive addresses and receive them there? can improve the ux, generate random keypairs can be a mess in terms of storing them, can be a sort of nutpayserver
Feels great to be building a small part of this Nostr-Cashu synergy with nostr:npub15dc33fyg3cpd9r58vlqge2hh8dy6hkkrjxkhluv2xpyfreqkmsesesyv6e. 🤝
