nostr:npub1n0sturny6w9zn2wwexju3m6asu7zh7jnv2jt2kx6tlmfhs7thq0qnflahe

Reply to this note

Please Login to reply.

Discussion

Unverified means the zap receipt is not coming from the wallet provider published on the recipient’s profile

nostr:npub12ekpvme6m2cv37a9mgq4kzemej8tx6ttg40j582rh77ewpvkg65qj8tq0f the pubkey that the coinos LNURL server returns doesn’t match the pubkey that broadcasts the zap receipts.

Pubkey that the LNURL server returns is b38877ef65530f09e6db43bb8ec141c38cd01f9a6436d563dddcc3b156a01365

Zap receipt is published with ba80990666ef0b6f4ba5059347beb13242921e54669e680064ca755256a1e3a6

Looks like that first pubkey you mentioned (the incorrect one) corresponds to the Pubkey CoinOS has assigned to my account.

Ah. That’s not correct. I just filed another issue. It’s supposed to be the pubkey that is being used to broadcast the zap receipts. Now I understand why no one has been using coinos as their lightning address on nostr. I think their LNURL server was never correctly set up for zaps.

I hope they’re ready for the next zapathon once it’s fixed 🤣