You are viewing a single comment's thread from:
RE: Why did STEEM blockchain froze ?
IT seems, the account could belong to netuoso:
2018-01-06, 00:47 netuoso bittrex 43.528 SBD f62cb7ea66e84c94867
2018-01-06, 00:47 nijeah bittrex 26.663 SBD f62cb7ea66e84c94867
they used at least the same bittrex address
no clue - but this is a bug worthy of a big bounty. I wonder whether STEEM has a bounty program.
Is there anything @ned can do about this?
This was actually a very minor mistake with huge impact and for the time being it’s fixed by
preventing existing negative withdrawal attempt
future attempts are also prevented
A better, ie faster fix will be provided in HF20 as per the comments.
This is one of those very unfortunate bugs that exists in all software.
Neither @ned or anyone else can prevent things like this and I would consider this a minor error. I think we must appreciate the long hours the unsung heros - the developers, @vandeberg, code reviewers and DevOps Team has pulled to fix this bug.
A simple "validation" check should fix it. Why it is not implemented in the first place. We are joke due to this programming error.
@yehey - While this could have avoided with a validation error, since the blockchain managed to work without hitting this error itself is a proof that its not major one. This is like a rocket launch failing and I think we all should realize that the software systems are prone to fail no matter how much quality assurance is done. While its bad that this happened, I think we should look the ability of the team to come up with a working patch with only minor chain base version mismatch in such a short time.
To Err is common but to fix them so quickly desrves some good words in IMHO
All credit to @vandeberg --> https://github.com/steemit/steem/pull/2583
I consider it MAJOR if the blockchain stopped working for hours, don't you think?
We can't sugar coat this incident. I understand you but in the world of business this is really bad.
yea, in the world of business, its a serious one :-(