This happened only when I enabled, even passively, nip05_verification. With it disabled, the error doesn't happen.

Reply to this note

Please Login to reply.

Discussion

No replies yet.