if btc did not fork(split) on august2017..
then btc would be using the exact same
block format as pre august2017.
transaction formats as pre august2017.
network topology as pre august 2017

but no, btc forked/changed/split in august. meaning a 2 way split.
both went in separate directions to the pre august 2017 protocol

go ask Luke JR why old nodes need "bridging nodes" to translate the full block data
go ask GMAX why old nodes need "upfilter nodes" to translate the full block data

especially how after august. a full archival blockdata is only relayed between peers using
MSG_WITNESS_BLOCK
and the 2009-2017 MSG_BLOCK no longer relays a full block data.. it only relays a stripped version (analogy: translated to pidgeon english from dutch)

analogy
august 2017 the blockdata changed from english(legacy) to dutch(sipa's prefered format) which new nodes can relay using the new MSG_WITNESS_BLOCK
legacy nodes that send MSG_BLOCK dont get the dutch data as is.. instead its a dutch TRANSLATER(segwit node) that strips the blockdata and changes it into pigeon english. which is not 100% accurate/validatable by english(legacy nodes). but deemed close enough to ignore the issues it cant understand

this does not mean the blockdata is legacy compatible. it means a segwit CLIENT has to be used as a translater
bitcoin (network: the blockdata) is not compatible... it needs a translater(segwit client)

bitcoin WAS the blockchain. but now because the blocks are in sipa's prefered format that cannot be just downloaded from a torrent as is but needs sipa's codebase to be a filter/bridge/translator for legacy nodes..
this does not make bitcoins blockchain compatible. it just means core as a TRANSLATOR can pidgeon english the data to trick legacy nodes into thinking the blockchain is acceptable. yet legacy nodes cannot fully validate very transaction clearly, nor can legacy nodes relay this new data as is. thus not compatible.

again the blockchain is not the same as pre august and legacy nodes are not part of the relay network. thus not compatible

P.S
carlton banks is a fanboy not a codeboy. its useless asking carlton about code, so ask luke/gmax/sipa
also i do laugh at the lukes many backtracking statements(2mb bad.... 4mb good). but if you ask him a straight question. using words that cannot be denied as they are in code. he does eventually admit the truth. so be sure to mention how full archival data is no longer served via MSG_BLOCK, and he will have to admit things have changed and when they changed. thus admitting the fork of 2 directions (bilateral split)

Some explorers still show "unable to decode" for segwit addresses. They aren't clickable in blockchain.info

https://blockchain.info/tx/f808c5ec3e1cefd2d3a9153128344b4f043bb2507274115b4cb2d839a72b93fc

Anyway, recently Jihan was asked: "Why are the miners still supporting Bitcoin Core? Is it just a short term profitability play?", he answered: "Yes, exactly."



Is Jihan serious about BCH or he is using Ver and Craig as useful idiots to milk it while it lasts? or some or none of them are serious and just want more BTC?

edit: Well this is off topic tbh, I was too lazy to create a thread on that or search a thread for the specific subject, I need to go get some sleep now.