Sort:  

Sadly have to agree... This HF feels like a complete fail for now... And i am afraid more bugs may come with the time... I just keep hoping for the best

I've been trying to stay optimistic in the past 15 months I've been here. It seems like the deployment of this hardfork was the single biggest oversight I've witnessed since I've been involved with Steem.

I know it's easy to complain, but if something huge doesn't change regarding development organization I won't be able to support this blockchain that strongly with confidence. From what I've seen, there's a ton of resistance to change. Does DPoS have to mean a close-knit circle which any vocal dissenters are kicked out of? Because that sucks, people that see things differently are often times the most helpful to the overall success of a project.

I know finding competent blockchain developers is tough in any case since it's such a new field. But as an investor I'd like to know if there are dedicated segments of the team, like a unit for testing out and introducing new code, a unit for monitoring current code, and one for extensively using different testnets to make 110% sure there are no major issues.

Maybe they have these, but the communication is poor so that most people are in the dark. From what I've gathered, if you're not in the top 20 witnesses, even some of the most talented developers and witnesses are totally in the dark!

I also wish all of the top 20 witnesses had extensive developer knowledge, I mean, isn't that supposed to be one of the main requirements?

It was the job of the witnesses to say no to the code if they didn't feel it was safe.

That doesn't work with the "fake nice" problem I was talking about. Witnesses have the same problem, they are afraid to make their own decision as you will lose witness votes if you don't conform to the decisions made by the top 20. There are other issues at play as well.

Not quite that simple. Top witnesses participate in a secret slack and are all on board with whatever goes on in there. I just know of it... I've not seen it, nor been invited to it.

I don't know what that has to do with reviewing the code before deploying it? Maybe you can explain.

The new code can be deployed and the fork accepted by a super-majority of the top-20 witnesses. The rest of the witnesses do not factor into it. If those witnesses outside of the top-20 do not then upgrade to the new fork, they will effectively become defunct.

So, sure - anyone can review the code. But if the people in the top-20 are going to blindly accept it anyway, there's nothing that the rest of the witnesses can do. You either go along with it or shut down your node.

And if you're in the secret Slack, you play by Ned's rules or you're ousted. So...guess what those people decide to do?

Actually, I've mentioned you twice this morning. I saw that you actually posted and discussed your concerns. I think that was the right thing to do.

Even if I don't always agree with all you say and do, you acted with integrity on this one.

Yes, @ats-david had a very in depth post on his blog about his concerns that I really didn't see elsewhere. I was surprised he was one of the tiny few.

There are too many lines of code to look for oddities... It's humanly impossible to study.

The only way to test it, is to run data through it. Not just "live" data as @timcliff mentioned in a previous reply to me.

(Apparently testnet gets live data sent to it, the same data flowing in the steem mainnet)

...but tainted data. Horribly corrupt data. Throw everything at it.

There are too many lines of code to look for oddities... It's humanly impossible to study.

This is correct when there are massive updates that are backed up for over 18 months and pushed out by the devs as a blob. It is not the case when there are smaller targeted updates (such as the one release a few months ago to address some json spamming attack). The latter are more closely scrutinized by witnesses (not all of whom, but some of whom, have a software development background and are capable of reviewing code to a reasonable degree). Carefully reviewing and second guessing 18 months of design and development work that occurs largely behind a private and opaque process just isn't possible.

Either we flat out reject the release and insist that it be (re)packaged in small bite size pieces to be individually approved (and indeed a minority of witnesses is strongly in favor of this approach) or, absent some known, identified reasons to reject it (for example, stability considerations prompted by the recent crash was seen as such as reason by a minority of witnesses) or we pass it through on the basis of assuming that the dev team is competent. (If they are not, then the Steem community ought to be seriously working to replacing or restructuring it). All of which needs to be considered as a tradeoff between conservatism and 'best practices' on the one hand and the practical consideration of availability of upgraded features on the other (and numerous devs and community members were communicating to witnesses how important many of these upgrades were perceived to be, representing a clear incentive to get them rolled out).

Mostly, things are working now, and the upgrade glitches lasted about 1 day (exchange downtime is fully up to the exchanges, and nothing prevents them from being up; the necessary fixes was released to them yesterday). Whether getting the feature improvements out in deployment was the right call relative to stability risk will be something that time will tell.

There are too many lines of code to look for oddities... It's humanly impossible to study.

Exactly what I thought when I read that last pre HF20 post by Steemitblog.

Cg

Yes, I agree. I'm going to be looking at changing my witness votes around significantly (but does it even matter when @freedom can strong arm anyone it wants into the top 20?)

Someone who has millions and millions of dollars worth of Steem at stake should have a much bigger say than you. However, your votes absolutely do count (just not to the same degree, as it should be), so please use them.

Of course that makes sense. And yeah, I always use all 30 of my votes. Shifted them around quite significantly today, too, based on what I observed during the past couple of weeks.

I wish we could revisit some of the suggestions made in this post from 10 months ago where @steemitblog asked for input, and then seemingly very few or none of them were implemented.

I especially liked the idea of an adjustable slider for curation % on posts. If not that, I believe an increase in general is needed, either to 33.33%, 37.5%, or 50%.

As with everything there are tradeoffs. Community input is great, but at the same time a full time dev team has its own (hopefully) coherent vision on how the system should evolve. Possibly, such a coherent vision is preferable to a hodgepodge of (even individually good) ideas. Some community-sourced ideas can be implemented without disrupting a development roadmap, but not necessarily all.

If you feel strongly that the approach being taken is the wrong one then please continue to express that (including via witness votes, but not only that).

Yeah, I know what you mean. But, with all due respect, what we have now comes off as a hodge-podge of random ideas thrown together. Devs aren't renowned for their social skills, but it would be nice if there was a whole liaison team that tried to convey that vision to the overall Steemit community, not just @andrarchy. Maybe then it would seem more cohesive.

I guess a major difficulty in the whole thing is that it's hard to bridge the gap between programmer knowledge and concepts a layman can understand. Nonetheless, I'll keep doing my best to try to grasp why things work the way they do and keep questioning if they really ought to be that way. Thanks @smooth.

Likewise thanks for the discussion.

Speaking of shifting witness votes around, I have not been able to unvote witnesses for months now. Once I vote for a witness, trying to unvote them just makes the upvote icon spin for hours without actually unvoting them.

Yes, I'm logged in with my active key,

Do you have any idea how to fix this? I've contacted github about it an never got a response.

Hmmm, that's very odd. I've never heard of that and don't know of a fix, but let me ask around @luzcypher.

@freedom uses @pumpkin as witness voting proxy. For the top 20 witnesses, @pumpkin voted 17. Without @pumpkin's vote, 13 witnesses won't be in top 20.
The conclusion is our votes do not make difference.

Slowly getting through the debates here and... please consider @stem.witness - the brand new witness from @steemSTEM. We have a new Standalone app on the way and an unimaginable amount of stuff coming up!

I think with/after the upcoming SMT hardfork (will it be a HF?) many of us will decide wether to stay here or leave. Stinc needs to get their shit together.

Yeah, and I agree with @ats-david and others who question whether SMTs is even something that matters at all should even be done. I'd be more likely to care about things that make STEEM more attractive and useful to the average person. Communities, improve the front-end, video hosting, third-party built in instant messaging, Android and iOs apps, etc. etc.

Also why do we keep the ridiculous reverse bidding system at all? It's so confusing and counterintuitive to have to wait to vote on something for your vote to be effective. I know it's to counter bots being able to snipe everything at minute zero, but 15 minutes is still too long in our fast-paced culture.

Yeah, and I agree with @ats-david and others who question whether SMTs is even something that matters at all.

My concerns about SMTs go far beyond whether they'll "matter at all." I actually think that they potentially represent a huge risk to the Steem blockchain and its users, both legally and financially/economically.

When you start introducing the possibility of ICOs (many of which are considered "securities" by the SEC) and an internal token exchange (where each exchange of a token may be considered a taxable event by the IRS), you begin wading into territory that is begging for government scrutiny and forced compliance from regulators...the very things that these blockchains and cryptocurrencies were supposed to try to avoid.

Not to mention the fact that the ability to create shitcoins and trade them on the blockchain will add a potentially enormous amount of bloat without necessarily adding any real value.

It's a huge risk that should not be considered lightly. And once it goes forward, there's no rolling it back, because of the financial and potential regulatory aspects of it.

I am very happy I vote for your witness.

Steemit suffers from the same failings most businesses fall into such as exclusivity of hierarchy, lack of communication, and partial deafness. It is important for the flaws to be pointed out in hopes of or in an effort to enact change. The more voices constructively talking about those flaws the better i think.

this is my feeling as well. with SMTs come things like jerrybanfield coins. A whole wave of useless tokens that get one person rich, where they cash out and move to the next scam.

how will SMTs incentivize an average user to adopt steemit, as opposed to addressing that some 95% of value on the platform is held by some 1%? or that nobody actually reads anything on here?

Which jurisdiction is Steem the blockchain under? Is each node under the jurisdiction of the country/state/whatever where it's physically located? How are the witness nodes geographically located?

Shitcoin bloat is a huge concern of mine. What people ate just dying to make their own new tokens? Scammers and fools.

Posted using Partiko iOS

I always felt SMT's were based on the premise that we live in an ideal world where everyone happens to be an honest entrepreneur who sees the potential in monetizing a comment box on Quora.com or whatever.

But using Steem as a sociological experiment, we can really get a great perspective to what huge extent individuals on a global scale are willing to milk, milk, milk at every corner. SMTs are going to be an open floodgate... to what, remains to be seen...

(Vote our new @stem.witness - witness of @steemstem, your favourite circle jerk)

freedom's identity has been discussed a couple of times previously, still no one is sure. Isn't it either Dan's or Ned's?

I also wish all of the top 20 witnesses had extensive developer knowledge

Big shock when I found out yesterday.

Hum !
Is he part of the top 20 witnesses ?
If so we know who he is.

I was waiting to see what you have to say as soon as you got a post through, I assume there will be more in the coming days.

So sad, and so true...

Everyones VP being reseted to zero was a big fuckup.

People leasing steem, and projects like utopian, are in a really bad situation now...

I am getting screwed. I paid for leases that are completely useless. I was barely covering them in order to grow the cycling community. Now I'm just out on my investments.

Yep. What company would feel safe having millions vested here and having this happen. Then they're told "don't worry, your funds are safe!" Ummm... except for the thousands of dollars in revenue that were lost by 1) downtime 2)resetting VP to 20%. It's a joke.

That's the obvious reason that a complete power down needs 13 weeks...it's like a prison
Serious investors would have moved their funds asap after this mess (at least those who would also be active in Steemit too and not only steem)...and one more reason serious investors won't power up...meaning steem's price will need way more than we think to climb high...
Just saying...

It takes every ounce of self-control for me to be rational on this, because I essentially lost six figures by believing in STEEM and not powering down in December. Whales lost MUCH more. Prison, for sure: though one of our own accepting, and it does provide the useful safeguard against people dumping STEEM when things like just happened occur.

I can imagine....
Reduction of that 13 week period would be a huge step to steem's success if you ask me. Because lot's of steem holders are also Steemit users... There are cases that you feel that you just don't have control over your funds...

did you know that the power down was originally 104 weeks? legit 2 years

I'm just going to chip in here. As you mentioned @ssjsasha the original powerdown was 104 weeks.

The thinking behind it is that it works as a delegated proof of stake. In other words, other investors gain confidence knowing that Steem cannot be dumped uber quickly.

Don't forget that Steemit arose right in the midst of the pump-n-dump ICOs. Investors come in, buy up loads of ICO coins. Devs and their friends dump coins and leave all the new investors (bag holders) high and dry.

So 104 weeks was considered a great way to show investors that this wouldn't happen with Steem.

It was later forked to 13 weeks, along with other changes to SP that gave holders of less than 100,000 SP a vote that would register over $0.01.

Imagine if you could just take out all your Steem at once. Can you imagine what the price would be doing right now?

13 weeks is not a prison. You go into it with your eyes wide open and it is not that long. Obviously it leaves you vulnerable to downward price fluctuations. However I think they'd be far greater if everyone was trying to take their money out all at once.

having to buy bitcoin, dogecoin, lightcoin or dash first then invest that coin into Steem is another. Looks exceptionally shady to not be able to directly invest.

That is neither shady nor unique. There are plenty of legit coins that you can only buy with other crypto. In fact most of them fall under this category, and it is very much the decision of the exchange where the Steem is held.

Ho hum, anyway, I agree with the both of you that HF20 was a disaster. Plus not being able to sell was particularly annoying. Hopefully in another few days it will be like nothing ever happened. 🤞😉

Cg

I was one of the people who sadly invested at around 600000 satoshis... almost 2 bitcoin worth... I was originally going to put every paycheck into steem power until I reached 10,000SP...that goal is still in my mind but instead I am waiting a bit longer before I start

You've hit one of two nails on the head as to why I've not invested into Steemit. The other is that it's not exactly easy to directly invest into, having to buy bitcoin, dogecoin, lightcoin or dash first then invest that coin into Steem is another. Looks exceptionally shady to not be able to directly invest.

Shadier still not being able to withdraw my investments earned quickly.

Even shadier still with the development being shite like that. A crash a week prior, then the HF20 fork screwing things up further, it's a trainwreck. It's why I'm going to automate my posting after today. Setting up all the automation now.

ahh dude.. it's not just STEEM it's bitcoin in general. Just being "fair"

  • but yes STEEM has a very narrow pipe-dream vision. SMT's are like the second coming.. and coming.. and coming..

still waiting.

Yeah, I would have lost it in any crypto. And I was being stubborn to sell like "Why should I hold it in USD? I don't believe in fiat!" but I didn't realized how dominated I was by emotion on that. Because I could have bought back 5 to 10x what I had in crypto.

same when I bought gold back in 2009. Fiat games are the standard. Just have some insurance in both crypto, gold/silver/metals, and even CASH. If Japan can do it for 20+ years, the USA can do it as well. I have written numerous 0.20 cents articles on steemit about if I cannot go int a grocery store and pay with crypto.. then it's strictly insurance/speculation/asset whatever. Sure it could go up +++ but that's the speculation part.. and I ALWAYS have to cash into local fiat currency to eat.

remember I said I wanted to invest every paycheck into steem power until I hit 10,000? well I have not started yet... my gut feeling hasn't told me to invest yet so I will continue the waiting game.... large upvotes are still welcome lol

I'm a little bit scared to invest by this point...

The witnesses have just as much responsibility as SteemIt, Inc. If they had issues or weren't comfortable with the code they shouldn't have dropped it, I really think there needs to be a post-mortem review.

I know we will sort it out, but it certainly made me thankful I do not hold a large stake. If I had a couple of million on here, I would have been sick.

Witnesses have expressed a lot of concern about the development process, especially the delivery of 18-month bags of code changes by one company operating mostly in private (albeit with some degree of partial visibility via github) as one single hard fork release. In the end it becomes a take it or leave it decision, where leaving it means that new features wanted by many in the community (for example, liquid beneficiary rewards, discounted/free accounts to grow the user base, etc.) don't happen either. I would say given 1-5 days of glitches where things are already working a lot better, whether the wrong decision was made is not really clear yet, but many would agree that the process is not at all ideal.

I have 3 k and I was sick... thank god there are places where you can diversify a bit.

Posted using Partiko iOS

You are 100% correct.... I learned the hard way.... I apologize. My stuff being stolen and posted in WEKU ... what a mess.

Embedded in every of your criticism, is the brutal truth. And I am really concerned why the powers that be ain't heeding your words of wisdom. Dammit!

You should have a say in the decision making in Steemit. I have realized that all your past rants are all making sense to me now.

Soon you’ll realize that it is not the fork that bends but yourself

Posted using Partiko iOS

Matrix?!

Posted using Partiko iOS

LOL spot on

Posted using Partiko iOS

The software was tested and we were aware that a normalization process would have to occur when the swith was flipped to HF20... However we grossly underestimated how long the normalization would take and ultimately didn't realize how vastly the RC implementation would slow things like posting and voting initially..

As a former top 20 witness and a current backup witness (who is in the "secret slack" as some put it) I'd have to state that we weren't exactly meaning to bring in these issues to the network and as stated above didn't foresee the implications that slowed the network down to a crawl shortly after the HF.