RE: The Curation and Engagement Leagues 🏆 - STEEM prizes & steem-bounty available! 🎁
I don't know, man. I think there are a lot of people who lost a fair amount of confidence in the Steem blockchain after yesterday's debacle. "There was a box that wasn't checked"? That's bullcrap. And even if it were true, that's not good news that you guys can't pay close enough attention to the check boxes that you forget to check the one that says "block fraudulent transaction instead of shutting down blockchain."
I'm not bullish on Steem right now. I know the price just jumped, but I think it's going to drop right back down again.
Then again, I think there's a price pump going on right now.
Being that the price is so much higher than the other exchanges, I would imagine that it's a group of people who are selling Steem back and forth at higher price levels to try to inflate the price and get the other exchanges to follow. That's just a guess though. I really have no clue.
I would say it's as good a guess as any, and pretty much what's been happening to date, and most recently with SBDs. Things seem to happen over the weekend for some reason.
You're the second person that seems suspicious about what really happened. I got in a conversation with pfunk after he asked me if I would rather the nijeah account get the 38 million SP or the blockchain shutdown, and that's when I said, I'd rather neither. He then let me know it was impossible for any software as complex as the blockchain to be totally bug free.
I get it. I really do. I think there's so much code, and there's more than a couple of people working on it and so there's moving parts, blah, blah, blah. But don't you think, once it happens, once someone does a transaction to vest themselves with SP, that it kind of opens the doors for others to try to come up with creative ways to get the blockchain to do something, or crash?
It just seems to me that you go looking at the payout operations and how many ways you could possibly mess that up, and then you go check the filter for those specific transactions and you makes sure they're airtight. I guess that's not how development works. You wait until it's broken and then you fix it. With a patch, in some cases, that makes things that were working just fine break. Okay, that's not what happened here (I'm just generalizing with every Windows update I ever did before switching to OSX. :)