Only 3 out of the top 20 witnesses support increased blocksizes; Steem Update 19.1 solution!
Steemit Bandwith Issues; The talk of the month
It feels like the talk of the month, the new users that are unable to post due to issues with bandwidth limitations. Many users has reached out to talk about this and tried to find ways to solve it. One, pretty quick, solution that was proposed by some are that witnesses increase the blocksize. This is just part of the equation, but determines how many transactions that can be put in one block.
So far only 2 out of the top 20 witnesses have increased their blocksize limit to the double, and 1 to 1.5x. Most of the backup witnesses have increased to the new double limit that has been recommended by many. The size isn't increased until there is a concensus among the 20 top witnesses, and it seems they don't think the change has been required.
You can see all witnesses settings on SteemD Witnesses Stats.
It makes you wonder why.
There has been no shortage on posts on the topic. Here are only a few in the recent days.
@neander-squirrel writes a very good explanation on the topic in "The Big Bandwidth conspiracy? No, not really:)"
@someguy123 askes all witnesses to increase in "Dear Witnesses - Please increase your block size!"
@reggaemuffin talks about how witnesses helps in "Bandwidth Limit Exceeded? How Witnesses Help You."
So as you see there are many discussion on the topic.
There is a long term solution in the workings as @timcliff writes about in "Potential Bandwidth Issue Fix is in the Works - Softfork 19.1"
With Steemit GitHub Issue 1257 the issue will hopefully soon be solved in a better way.
All witnesses should stand on toes to make sure they put the new version online when it has been approved and released for live usage.
Important to vote in active witnesses
I can't stress it enough. This is where YOU and your 30 votes come in. Every user has 30 votes that can be used to vote on any of the witnesses in the ~witnesses page. The vote can be revoked at any time and cast on another, no penalty for raising your voice on Steemit.
Support me as witness on Steemit.com and BitSharesSteemit: sc-steemit 
BitShares: sc-ol 
Proud Supporter of the Cryptocurrency Gridcoin
BitShares: sc-ol
Proud Supporter of the Cryptocurrency Gridcoin
I am have only voted twice but i am gonna vote for some witnesses that want big block size.
Good :) It's your free choice when it comes to decisions on the network.
Ya never looked much in to them i have voted for 2 i knew and have talked to but i am gonna look into them more as bigger block size and other issue that may raise.
wow, when I wrote my post, almost all of them was used 98k size.
Does it have any cost to run your node with higher settings? I don't understand why is it not popular with them?
Thanks for the positive words about my post @sc-steemit!
Sharing to gather more to act!
Thanks for sharing. Your post is worth more!
Need more upvotes? Read our post https://steemit.com/steemit/@emble/worked-hard-and-your-post-got-only-a-few-cents-think-your-post-is-worth-more-learn-how-to-get-more-upvotes-and-more-value-for
Good luck.
thx for sharing
The latest recommendations are to reduce the blocksize to normal 65536 again.
Due to the fact that a high blocksize might cause an overflow bug to trigger, all witnesses are going back to minimal block sizes.
An updated version of Steem is in the works, 0.19.1, that will mitigate the issues better.
meep
meep
cool! Great content @sc, which scenario could happen for eth after segwit2X is implemented for bitcoin?
thanks for the answer and i am following you now and upvoting you!
Please don't spam the network. This post is the only thing you write as a comment everywhere.
Flagged due to this.
Thanks for it @sc-steemit, i just wanted to gather more information from different possible crypto-user before the hard fork in August or the integration of segwit2X process.
I am try to write a blog a the moment including all different opinions that i get, that s it! I think it is useful and hopefully in the next days you will see the result.
Why i am doing this? because i found that is very difficult get commented in a previous post about that so i try a way more "manual" to get their qualitative answer.
Let me know what is your thinking about and if there are way to be more efficient gathering qualitative feedback from the steemit users.
thanks
Francesco
Thanks for it @sc-steemit, i just wanted to gather more information from different possible crypto-user before the hard fork in August or the integration of segwit2X process.
I am try to write a blog a the moment including all different opinions that i get, that s it! I think it is useful and hopefully in the next days you will see the result.
Why i am doing this? because i found that is very difficult get commented in a previous post about that so i try a way more "manual" to get their qualitative answer.
Let me know what is your thinking about and if there are way to be more efficient gathering qualitative feedback from the steemit users.
thanks
Francesco