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
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
Uhh... didn't Classic already "release the code"?
Isn't the point of this thread that no one is using it?
LOL?
but Classic represents a change in government. miners are willing to avoid this by making an agreement with core, in that core will eventually( in 2017) support a block size incress to 2MB
core seems to have 0 intent on making good on their agreement
and are trying to BS their way out of the agreement.
saying things like " TECHNICALLY we didnt agree to anything
"