I was wondering if this is what you were referring to in the post. From my notifications, the bug started 20 days ago so seems to predate your changes made last week, maybe that is useful to help track it down.
I was wondering was it creating digital dust on the blockchain or worse still forking it backwards in time.
You are viewing a single comment's thread from:
Do you have a link to an error from that time? It would be helpful if so, since I think we deployed the new code on the 19th (i.e. 10 days ago). But it was probably running on another server prior to that and we initialized our server from that one, so I would also need to get the date when that one was setup. Nevermind, I guess I can just look at your notification history, I didn't read close enough the first time!
Here is when the bug seemed to start for me. 20 days ago as far as I can tell. I am connected to hived.emre.sh node run by @emrebeyler .
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.
I see. I will try another node and see if it resolves it. Thanks for the interaction.
I checked your notification history, and unless I misread it, the first occurrence was 9 days ago, which fits in the window for the code update on our server. Still, that's helpful since it seems to confirm it was probably the new code.
first one that i seen was 9 days ago too.
Thx for the confirmation.