nostr:npub1ghcetnluhryhynhuyj8s2pazldjm27wl40nu6dfeskvpv09twcnsneygat I am 94% sure that nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s is correct and this was a subtle error with our implementation. I am rolling out out a fix now. Will ping you in about 5 minutes so we can test the fix.

Reply to this note

Please Login to reply.

Discussion

Excellent. Thank you everyone πŸ’œ

I’m also 92% sure I understand why our monitoring and tests didn’t trigger the error.

nostr:npub1ghcetnluhryhynhuyj8s2pazldjm27wl40nu6dfeskvpv09twcnsneygat now 99% sure that nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s was right, and our implementation is now fixed.. I just ran some tests on my end and the thing that was previously failing is no longer failing.

Thanks everyone πŸ’œπŸŽ‰

we give out how you did it

I see zap notifications now πŸŽ‰πŸ‘

yay!