The masses decide what 'Bitcoin' is by the adoption and usage exactly how they decide what their search engine or web browser is.
With SW as a SF BTC is a fork as well and it might be the NetscapeAltavista for the masses.
It still follows the same chain though is didn't fork off you decide it is not forced on you if you don't trust or want to use segwit then you don't have to you decide by the type of address you use
If you carry on using legacy addresses then you are using the exact same Bitcoin as you were several years ago nothing changed in that respect the data is still stored in the block in the exact same way as before.
The only time the data structure changes is when you use a segwit enabled address which in laymens terms just moves the signature data from the transaction field to a separate merkle tree that's pretty much it
Again, isnt that because it was closer to a uahf, disguised as a uasf.....in order to prevent a fork off...which led to segwet coin being called btc and retaining the ticker...
As for ltc, did they need a segwit malleability fix aswell in order to use LN?
The system that was in place was for miners to signal when they was ready in order to activate a improvement this was not a issue when Bitcoin was early and spread out but since asics and large pools becoming the norm it was getting abused as any miner with over 10% could stop something even if 90% agreed
UASF was just that users running a node that activated segwit without the miners so they had 2 choices come along or signal ready and activate which they did
And yes litecoin needed a malleability fix and chose segwit for LN
The nodes that do nothing and cost nothing to set up out voted the miners lols
The nodes activated a uahf, why do i say this....because a HF isnt forced on you...."follows the same chain though is didn't fork off
you decide it is not forced on you" tek
yea i thought litecoin may have had TM issues, was unsure on what cobbles had changed back in the day when making ltc....TM wasn't one of them anyways lol.
Why would litecoin have TM issues anyone can use segwit every Bitcoin fork now automatically has segwit code and litecoin didn't need lightning it wanted it to remain relevant
LN makes commerce simple I purchased some steam vouchers the other day from bitrefill took me about 20 seconds from clicking buy to getting the code email and activating it
Why would litecoin have TM issues .................. "And yes litecoin needed a malleability fix" your comment above.
anyone can use segwit every Bitcoin fork now automatically has segwit code .....yes it does , thats why bch is special like og btc, the only version that is segwit free (pleeeease dont start that clashit stuff lol)
litecoin didn't need lightning it wanted it to remain relevant ...id say ltc and blockstream took over and killed of btc the way it was meant to be but stole the ticker.
anyways forget ltc.
Back to this uasf/uahf, ...so you agree it was an uahf activated by useless ,free to create nodes.
Segwit it nothing more than a malleability fix yes it now allows for larger blocks but that was just a side effect
One of the proposed malleability fixes for BCH is very much segwit-like
Segwit moves the signature out of the transaction area into a separate merkle root that allows for backwards compatibility
BCH's proposed fix moves the signature from the transaction area just the same as segwit but simply moves it to the end instead of to a separate merkle tree but this means it must HF and nobody gets to choose it's forced
