Thanks. Next thing, dive into the algorithm.
Or at least point towards the algorithm that calculates this in the source. That would help me a bit further.
Why 25% of maximum blocksize?
Why did the witnesses agree on that? :)
At least the top 20 have to answer this.
If they are notable to do so, why are they in the top 20:))
Why not 30%, why not 10%?
You are viewing a single comment's thread from:
I explained the 25% in the previous post. I'm not a professional programmer and not a fan of C, those waters are treacherous for my boat lol. The 25% is not a witness parameter/decision, it's hardcoded in the steem code, it could be tweaked if the developers decide to do it.
Yes, I know it is hardcoded.
But the witnesses decide if a HF is used or not.
Otherwise, they are just the puppets for STINC and the developers.;)
Or isn't this one of the task of the witnesses?
I always thought they would decide, whether to implement something or not in production.
You don't need to explain, just link to the file/line
:)
I believe we should start increasing block size at 5% intervals. I also talked to @roadscape abut this, and the thinking is, the reserve is very volatile, so we need to increase in small increments, say 5%. Then see how it goes at and give time fr RR to balance out as we go.
This talks more about it also https://github.com/steemit/steem/blob/f762f1407f615c8e8fb3d4c9dec2f61801d4d5ee/libraries/plugins/witness/witness_plugin.cpp#L275
Thanks for showing these stats @drakos, great job!
If I'm not mistaken, the algorithm for
current_reserve_ratio
is in https://github.com/steemit/steem/blob/master/libraries/plugins/witness/witness_plugin.cppThanks!
That comment is interesting:
* If the reserve ratio is consistently low, then it is probably time to increase * the capcacity of the network.
Well, it might be the time right now, to increase:)
Don't worry it's C++ with templates. ;)