Ah, but that's on emre's node, not ours. On ours, it doesn't happen till later. I can only guess that maybe he updated to the experimental code earlier than we did (or possibly it is a different issue in that case). For sure our node doesn't show a similar issue until we updated.
You are viewing a single comment's thread from:
I see. I will try another node and see if it resolves it. Thanks for the interaction.