Quote from: Luke-Jr on May 26, 2016, 04:46:23 AM

Quote from: adamstgBit on May 26, 2016, 04:34:33 AM

so you're saying you think core will not/should not, add in the code required to allow miners to activate a HF with >75% hashing power.

Correct.

And even if we did, it would be futile, since neither devs nor miners can force users to adopt it.
It is literally technically impossible for miners to activate a HF period.

so core is saying that there would be no code release THIS YEAR to allow USERS to show they want 2mb.. to then slowly over months get to a certain saturation point of that would then allow the pools to move forward..
is this whole round table stuff just smoke and mirrors and that no one(users or pools) will have any code that has 2mb as an option untill summer 2017..

if so.. what is so special about summer 2017.. why not have the code available sooner (this year) and then activate when a certain circumstance is reached.
why of why does it have to be based on seasons of a year, instead of how prepared and ready the community is by actually having the code in place ready.

code does not care or understand the word "SUMMER" so a technology should not be hindered based on seasons. and instead have code ready and prepared to activate when a certain network saturation level is reached.

if i see luke JR mention that the HF is dependent on a date or season. and code will only be released based on such season.. then that to me is just him delaying it for no logically or technical reason. but based on human decision.

here is a hint.. even with the 1mb rule.. pools didnt just jump to 1mb instantly.. even today some pools just want to make 0.2mb blocks. so pools can have the 2mb code existing in their program. but have preferential setting to only make <0.998mb blocks until they think the users nodes can handle it without mass rejection.

if a pool makes a big block to early it would get rejected and they would learn their lesson..
no one can predict which date on a calendar to move forward. and delaying the option or possibility purely because you cannot imagine a particular date on a calendar is also a futile mindset..

in short RELEASE THE CODE and then let users run it... then later pools can start making bigger blocks when and only when they deem the saturation point has been reached that their blocks wont get rejected/orphaned. without having to check a calendar to find out when spring turns into summer.

RELEASE THE CODE AND LET USERS GET PREPARED AND START THE BALL ROLLING TO ALLOW POOLS TO DECIDE WHEN THEY THINK THEIR BLOCKS ARE SAFE TO BE MADE BIGGER

by stopping users from having the code your just delaying any prospect of pools ever growing. RELEASE THE CODE AND GET THE BALL ROLLING