Freakoverse on Nostr: Just realized yesterday, thinking of nip-99, that there should be, should be a ...
Just realized yesterday, thinking of nip-99, that there should be, should be a "receipt" function, unrelated to LN.
npub-A selling product.
Product has some kind of ID.
npub-B buys product.
Receipt (event address) is created, which has product ID and other info related to product, that's verifiable with npub-A address as the seller and npub-B address as the buyer.
This, the receipt event address, may include LN receipt information.
That receipt event address (addresses) would be stored in relays, however, depending on either of the party, it would be vital for them to always have that receipt event address saved, to verify the purchase.
I'm not sure if this is already a thing, but I think it's incredibly important to have.
I'd want to have it as a user and/or store owner/runner.
#nostr #nips #ecommerce #commerce
npub-A selling product.
Product has some kind of ID.
npub-B buys product.
Receipt (event address) is created, which has product ID and other info related to product, that's verifiable with npub-A address as the seller and npub-B address as the buyer.
This, the receipt event address, may include LN receipt information.
That receipt event address (addresses) would be stored in relays, however, depending on either of the party, it would be vital for them to always have that receipt event address saved, to verify the purchase.
I'm not sure if this is already a thing, but I think it's incredibly important to have.
I'd want to have it as a user and/or store owner/runner.
#nostr #nips #ecommerce #commerce