On Segwit not being backwards compatible question

[franky1]

back to the topic question

the blockchain format is not compatible backwards.

old nodes are not just relaying blocks along with everyone else byte for byte the same. they are not even relaying transactions the same.. the old nodes have been re-jigged around the network topology where they are just the tails/border/outer nodes of a network. that require segwit nodes to bridge/filter them data.

lukeJR, sipa, gmaxwell said it themselves.

also to prove it
if there was a fault with segwit nodes and they had to back date/downgrade back to a pre-segwit node
guess what.. problems would arise.
as their would not be any segwit nodes to translate(filter-bridge) the blocks
if people then accidently sent out segwit transactions whereby the network defaultd to non-segwit.. those transactions could be manipulatd.
(this is why although they pretend it was all soft and backward. the devs didnt release the wallets for segwit until after the mandatory split)
P.S.. by bing madatory and being a rule change requiring acceptance or rejected off the network.. that is not a soft fork. its a hard fork

and again ill emphasis it was a segwit block format that occured first in the timeline to change the concensus rule and direction.. which triggerd the rejecting of blocks and throwing people off the network

[1715674861]

1715674861

[1715674861]

1715674861

[1715674861]

1715674861

[1715674861]

1715674861

[1715674861]

1715674861

[Wind_FURY]

Before we start another long debate again, can you first tell us what are "bridging nodes"? Are they regular Segwit nodes that can communicate to non-Segwit nodes in a "language" that they can "understand"?

If there is a Github repository for "bridging nodes", kindly post it.