Is there such a thing as proof of zaps? Can I prove that I have been zapped, by providing a list of receipts?
Discussion
not proof in a self verifying cryptographic sense. zaps require you to trust the lightning node that is creating the zap. the node could lie, so there’s no way to know for sure if a zap is “real”, unless its coming from your own node.
How does Lightning itself confirm payments? The Lightning node is just missing an API, right?
https://github.com/lnurl/luds/blob/luds/16.md
via lnurl. invoice requested by zapper, invoice paid by zappee
here is a better explanation https://nostr.how/en/zaps but the only evidence is a successful zap is if the recipient publishes the 9753 event kind
You need to know the state of the bitcoin blockchain. Lightning channels are offchain multisig bitcoin transactions. You can only truly verify if you are one of the two parties involved in the multisig channel.
nope, all zaps can be faked (but that's ok)
nerd plug, NIP-61 nutzaps are "verifiable" is you trust the mint
It would open up doors if we could prove that somebody zapped somebody else. We could actually allow them to "spend" their receipts as a secondary currency.
not sure that is needed. you can spend the zapped sats if you received sats and if it was all fake then there is nothing for you to spend
My idea is to have a virtual pet that grows the more you get zapped. You would publish essentially a "skill tree" event, where you allocate "points", and those points come from verified zap receipts.
who would control the pet? if it was a server with an lnurl pay then you would be registering the sat invoices on your end as the users paid. only you would know if they were real zaps but since it was a centralized service it would be ok
I need this.
"Bitgotchi" or "Satoshigotchi"
A Zapagochy 😆
nostr:npub12z8jsett3k6rv9fa2guau5p540qr2xuvjzkr8e432mglafjt99sqkw9zmx you’re about to get a dragon and who knows what else.
🐲🐉
make it happen
ok you're crazy and I love it.
cashu zaps are payments locked to a public key and posted publicly (there are no receipts, the zap is the receipt).
can’t prove that someone zapped someone else. zaps are most reliable for signalling to your client that someone has zapped you for something, assuming you trust your zapper.
that's how NIP-61 works. You don't need to trust the zapper or the zapee, but the mint, for zap verification
Sounds a bit like the totem. nostr:nprofile1qqswwud0pvzu362lehm0av6sq4zd97cue5uy0z8f7jgtk0hz368dvmcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszxmhwden5te0wa5x2ct59e5xzurs096xzan9wfhzucm09uqsuamnwvaz7tmwdaejumr0dshsdms043 and nostr:nprofile1qqsypwwgtll74lqu4huvxzjwtjyxvrlkujt35rw8y026ke6ttesmg5gpzemhxue69uhkummnw3ex2mrfw3jhxtn0wfnj7qghwaehxw309aex2mrp0yhxummnw3ezucnpdejz7wzpxlr are already working on something along these lines...