I've seen it happen, once. Please do the faddat / JSON search here.
Additionally, l0k1's seen it happen.
Additionally-- I tried your tool. I don't think that it got everything or if it did, didn't get it in the right format.
Details, yes. Important details? Yes.
Oops-- it was a piston error. That time.
Fixing up Steems' API would have resolved that in no time. But never fear! The gRPC API is nearly here and it talks gleefully with the front end in real time. Everything else can go much more smoothly from there.
Ok, so we have you on the blockchain claiming that it was a rare situation that is impossible to recreate. And my tool also just happened missed it on those exact same occasions. Got it.
Incorrect.
Ya know what man? I won't tell you about it. I'm back off to my grpc-itude. you'll see.
How was it a piston error?
And now we're into questions I don't have the answer to.
It was a piston error, because xeroc said it was.
No he didn't.