meaning people choose the consensus option in their own time, even years before and happily run their implementations before activation to do their tests and just use bitcoin happily. knowing it only activates when 95% of other people also agree.
and after activation only 5% need to decide if they want to be a full node.
Isn't it possible to start the process now by running Bitcoin Unlimited? I do not see why there is a problem except that some supporters of the hard fork are in such a hurry for bigger blocks because they think the users will increase. Bigger blocks will also open a door for other problems like the storage problem and the bandwidth problem.
'2mb blocksize' is less storage and bandwidth than '1mb base 4mb weight'
its literally simple maths: upto 2mb or upto 4mb..
thats the hypocritical thing.. core are actually the big blockers.. they want 4mb of data.. the strange thing is. by limiting the base to 1mb the total growth of serialised (complete) transactions is only 1.8mb capacity. but that then lets them fill the remaining 2.2mb of buffer space with non tx data. such as arbitrary codes for other features. EG you can fill that space with an invoice or write a book, or a reference to some mundane data..
meaning lets say 1mb block ~2500tx
1mb base 4mb weight ~4500tx (1.8mb bloat)
1mb base 4mb weight ~4500tx + arbitrary bloat code data (4mb bloat)
meaning core wants 4mb of data but still only ~4500 transactions (not legacy transaction, it has to be new segwit tx's to get that level)
yet nearly everyone else sees the logic of 2mb ~5000tx.. and later 4mb ~10000tx of legacy transactions
but hey seems segwit it being ploughed through anyway. so the next logical consensus is
2mb base 4mb weight
so that segwit still functions but we can then presume to have ~9000tx ... but im sorry core, no spare space for them non essential codes to bloat up. thus keeping the blockchain lean and clean and used for transactions (which they wont agree to(facepalm))
as for the question of BU.
BU has been ACTIVELY running since last year. so has bitcoinj, xt, classic and many others.. these have not demanded a 14 day flag and 14 day grace to be active by christmas.
BU has just been open for anyone to use and if at some point 95% of nodes have a similar open consensus of dynamic blocksize increase and it reaches 95% agreement.. then it triggers the miners to also do a 95% flagging event. (giving more time for nodes to get more then 95%)
and then a grace period (giving even more time for nodes to get more than 95%). so by the time it actually activates the percentage of nodes already upgraded will be well over 95%.
unlike core, change rules first then get nodes to upgrade second. thus rendering the nodes not full nodes without choice, and then rush to regain their full node status and have to move funds from legacy keypairs to segwits HD seeds, auditing funds and merchants changing their customers deposit addresses and double checking it all worked out fine (facepalm)
im not even sure why 15th november was even picked.. most people know it would/should have been a block number.. however by using a date instead, highlights a rush schedule based on human concepts of a calendar/deadline. rather than a natural flow based on technicals
again for the last year anyone can run BU, classic, xt, bitcoinj etc etc, test it, review it, play around or just run it..
but core.. hmm.. only a few days old and they are begging for christmas activation, requiring trusting the devs