Nostr Web Client

Today is a sad day. I gave up on trying to get started with zapping in a self-custodial manner and set it up with WoS, mainly to get a friend setup quickly, too.

Questions: I zapped myself from a test account that uses the same WoS ln address and there on Amethyst, payment failed with WoS but with BlueWallet it worked ... sort of. Now, in Amethyst I see 500sat zapped but on Snort I don't see it when loading and reloading that same note.

Can I receive zaps now or not?

(Also thanks to those who tipped me without the zap that would tell me what it was for. I'm not sure, clients made clear that those zaps would be anonymous.)

Leo Wandersleb 2y ago

So on Amethyst I see somebody zapped this 21sat. On Snort I don't see it. nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 is this a bug or does Snort not like that my two test accounts also use the same ln address maybe?

Reply to this note

Please Login to reply.

Discussion

faisal 2y ago

I snort zapped these twice successfully. Damus zaps didn't go through

Leo Wandersleb 2y ago

On Amethyst I see you trice in the list of zaps. I don't get Snort to show any zaps on this message.

Kieran 2y ago

I rolled snort.social back to an earlier version

Leo Wandersleb 2y ago

That fixed it. Thanks.

Kieran 2y ago

If you change your LN address your zaps will break because we cache the pubkey of the zapper (your wallets zapper key) in the profile, one way would be to manually delete the IndexedDB for profiles (snort-system) And it should get the new pubkey and the zaps will be valid then

Leo Wandersleb 2y ago

Opening the dev console, my firefox just needed a restart and the log was full of `Error: Uint8Array expected`. Now after a restart I also see this line with this stack:

```

14:52:25.648 Error: Uint8Array expected

bytesToHex utils.js:35

decodeInvoice invoices.js:24

a Zaps.js:11

parseZap Zaps.js:17

e Note.tsx:82

M Note.tsx:81

React 2

Pb Note.tsx:80

React 8

invoices.js:34:16

```

Leo Wandersleb 2y ago

Deleted that one table and don't see zaps after tab reload.

Leo Wandersleb 2y ago

Clear cookies and site data ... did not help neither. I see no zaps in Snort and log is full with the mentioned error.