franky1, Are you running a full node? If so....what client are you supporting? Is there any way that we can hedge our bets on the "off chance" of the occurrence of a fork actually precipitating very suddenly? I mean....I learned something with the ethereum fork....the newer chain gained the support and the older chain lost value....but there was a window there where both had equal value and some took advantage of that situation by acting quickly....What do the tea leaves say here?
i have my own. with a few tweaks.
infact i have core, my own(wrote in different language) bu, classic, bitcoin j and others. i play with them all depending on what im doing/testing
but in short.. if segwit activates.. BU, xt, classic, and al the dozen others 'brands' (if not biasedly banned by blockstreamers) will still get the filtered (trimmed) blocks. but obviously by not having segwit validation. will only be in the hodgepodge of second tier(downstream) part of the network but not fully validating segwit data.. and just relaying native tx's upto segwit upstream nodes..
essntially making BU classic, xt and older nodes just lite wallets.
but if BU, activates.
xt, classic and a dozen other 'brands' will all be ok ALL on same level.(no 2 tier)
but then core end up seeing orphans and banning nodes to ignore the orphan drama. thus stalling out core, forcing them to either
tweak code to join the majority (give in and raise the block limit).
ban nodes and only white list core nodes to start their minority coin
stay stalled and turn node off
if classic activate
BU xt and a dozen other 'brands' will all be ok ALL on same level.(no 2 tier)
but then core end up seeing blocks it doesnt like .. so orphans and banning nodes to ignore the orphan drama. thus stalling out core, forcing them to either
tweak code to join the majority (give in and raise the block limit).
ban nodes and only white list core nodes to start their minority coin
stay stalled and turn node off
i think the simple solution is for core to:
keep the TXSIGOPLIMIT at 4000.. that way no matter what the blocksize is, malicious TX's dont start making bigger sigops (EG cores 0.14 16,000 rather than 4000 - facepalm)
and core to put in a RPC and GUI options tab where users can reset the blocklimit live...WITHOUT needing devs to give in/spoonfeed. without needing to recompile.. so that users are more incontrol and adaptable to change without needing devs to decide for them if/when/how.
that way users can change settings at their leisure and become more independent
