Quote from: franky1 on October 25, 2018, 12:33:16 AM

Quote from: squatter on October 24, 2018, 08:35:34 PM

Quote from: franky1 on October 24, 2018, 02:00:53 AM

old nodes are not compatible. they are handed a pidgeon english translation.. theres a difference
its why even the devs clearly pointed out that old nodes become downstream/filtered(their buzzwords) nodes instead of part of the main relay network. they even drew a picture to make it easy to understand.

old nodes do not relay blocks to segwit nodes nor relay segwit transactions. they only receive a stripped down block and then sit on the edge of the network

If older nodes aren't compatible with Segwit, why can I send Segwit outputs to legacy addresses? Why can I receive payments from legacy addresses to my Segwit wallet? Why do older nodes accept Segwit transactions and blocks as valid?

firstly your talking about transactions. not nodes. (nice meander by the way..(facepalm))
learn about the network topology.

Actually, no. This pertains to both transactions and nodes. They are inextricably linked. Segwit nodes can send Segwit outputs to legacy nodes. Legacy nodes can send legacy outputs to Segwit nodes.

This compatibility has absolutely nothing to do with network topology. You're just fundamentally confused about what "compatibility" means, or you're purposefully being dishonest.

Quote from: franky1 on October 25, 2018, 12:33:16 AM

also older nodes do not accept segwit transactions as valid. the full validation check of a segwit transaction gets bypassed and is auto deemed as accepted. (not valid(there is a difference)) OLD NODES DO NOT SIGNATURE VERIFY A SEGWIT TX)

Actually, they do accept Segwit transactions as valid. If they didn't, they would reject such blocks. You may want to review how invalidity is treated on the Bitcoin network. Blocks containing invalid transactions are simply ignored.

Legacy nodes can't validate the signature of a Segwit transaction. So what? They still validate the POW, the inputs and outputs, the scripts, etc. Everything is validated the same way as before. Legacy nodes are just 1) accepting and propagating valid transactions from/to the network or 2) receiving valid outputs that have already been accepted by the network.

Your fundamental issue here is with how the Bitcoin protocol works, not Segwit.

Quote from: franky1 on October 25, 2018, 12:33:16 AM

imagine your a fully validating node. but you dont want to OPT-IN. you dont download the latest version to opt-in. thus you would think that you are a part of consensus giving a no to the vote.

"Consensus" = the Bitcoin protocol's consensus rules. It's not some sort of a democratic vote or something -- that's never how Bitcoin (or any network) worked.

Segwit is 100% compatible with the consensus rules, so there is nothing for your node to "reject." There is no voting. It's either compatible or not. You don't have any say over that.

If you think node operators should be able to "vote" on everything other compatible nodes do, then you don't understand how networks operate. You don't get to decide what the rest of the network does. You can OPT-OUT if you want by shutting down your "pigeon English" node, but that's the extent of your power.