As we said in the post, we have gained a lot of knowledge from this incident and know a lot of tools we want to develop to ensure this won't happen again. While the process might be unpleasant for you, and for that we apologize, this process of dealing with the unknowns and developing solutions is precisely how problems are solved for good. Building blockchains is still a new thing. Building blockchains that power real applications is something only we do. And building such a blockchain and updating it frequently is yet another thing only we do. We have no one to look to for guidance, no established model for anything. If someone tells you they can develop bug free code in such an environment, they're just a liar. What we can promise is that we will never release code that puts your important information at risk, and we have demonstrated that over and over again. This event was a consequence of that commitment as the blockchain stopped producing blocks specifically to safeguard what matters most. Those who come after us will be able to benefit from our solutions, but we do not have the same privilege. I am sorry we live in a world where we have to be the one's blazing the trail on this, but that's also why we are so committed to what we do. We've been doing this for over 2 years and our engineers and witnesses still respond at all hours and put in countless hours to fix the problems that arise. If you don't think that it is commitment, I don't know what is. And yes, for the people who do the real heavy lifting (i.e. not me) it is totally thankless.
You are viewing a single comment's thread from:
Hey, @andrarchy.
I'm glad to hear all of this. It is all pioneering on your part, and the analogy you gave me the last time of building the airplane as it's flying has stuck with me. It does describe what you're doing, and attempting to do. Something that is basically impossible to do (at least building a commercial jet in flight would be).
I'm glad to hear about the dedication and expertise employed after the fact. I've seen it in action. I know it exists. I'm glad to hear about the tools that you all want to develop to prevent such things from happening.
I guess since it's nearly ten years since Bitcoin rolled out I figured there might be a little more on blockchain technology out there, along with project management, product testing, etc. I thought there would be more to it as far as common practices go. If not specifically for the blockchain, at least adapting from other industries.
I know the STEEM blockchain is unique in many aspects from other blockchains that aren't designed to do what it does and will do. I can see the uncharted territory there, but I was expecting there would be something else to draw on, rather than it basically being put it together as you go. That's more than just building the blockchain. That's also needing to build all the procedures and protocols surrounding how it gets built. I figured there would be a lot of that in place by now.
I've never heard of anyone saying they can create bug free code. Developers are pretty united on that front, even ones who think they can do it better. So, wasn't trying to say that at all.
Of course we use established project management techniques.