I’m also 92% sure I understand why our monitoring and tests didn’t trigger the error.
Discussion
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.
