nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg can you give me a hint why this is?
Discussion
Maybe there was a connection issue between your node and the LSP? Restart, wait a few seconds, then try again? Otherwise, submitting logs to our GitHub could help us investigate.
It took some time, but it worked. Strangely, I had a vey similar issue on a second device as well. It also resolved itself after a while.
Mempool is coming down again. Weirdly enough that has something to do with it. We'll try to push out a release next week to partially address this edge case.