Where does that say it requires a retarget? It should't.
Well I suppose they have 2 weeks to uppgrade, until the difficulty retarget is changed, because the minority of miners will mine invalid blocks.
Where does that say it requires a retarget? It should't.
He's confused (whooooosh, lol)
He thinks that the 2016 blocks used to assess the difficulty re-targeting is the same 2016 blocks that evaluate fork signalling. Which is indicative of the rest of his attention to detail: there is no rationale for using the re-targeting window as a fixed timeframe within which forks are decided. That wouldn't make the slightest bit of sense: it's a rolling 2016 block window, irrespective of the difficulty retargetting window.
Nowhere, that is just How I envision a consensus hardfork to happen.
By using the difficulty retarged window, because if miners are mining on the minority chain, they are losing money.
So people are incentivized to stay on the majority chain. Therefore if 90% of miners and nodes agree to a hardfork, they do it, and then the 10% minority will be forced to join them,otherwise they will lose money through mining.
This prevents a chain split like Ethereum VS ETH Classic, because ETH has a 1 min retarget, while BTC has 2 weeks.
Yes you can, but that would not be Bitcoin.
No bitcoin is whatever people want it to be. Especially nodes and miners. If the software is uppgraded, then that shall be bitcoin.
There is nothing in this world that stays the same forever, nor should bitcoin.
Adapting to change is the only way to survive: Survival of the fittest.
If bitcoin cant adapt, it will guaranteed not survive in the long term.
Wrong. Let's evaluate:
1) You don't need 51% of nodes for a hard fork.
2) You can fork without any kind of support, i.e. we call those altcoins.
3) You could also split off with this kind of code with any % of hashrate as long as you change the right parameters.
You need that much to legitimize the hardfork, but it would still be volatile.
So above 80% would be considered more safe, maybe 95% as segwit requires.
Deploying and testing custom software takes time. If anything, 'a fast upgrade' would potentially cause huge financial losses.
You are misinterpreting my words.
I have said that it will take months to test and debug the software.
I only said that after the software is clean, then we begin the deployment phase, and in that time window, there will be 2 weeks for people to activate:
But I guess they will have the code deployed in the software, that will activate at an agreed date. So they will have months to test the software for bugs, and 2 weeks to signal the hardfork.
So up to 6 months of testing and debugging, then 1-2 months to wait for people to download the software, and then 2 weeks to deploy it and activate the hardfork (after a difficulty retarget).
A pretty conservative uppgrading roadmap.