|
|
|
|
|
by jude-
1985 days ago
|
|
The task of relaying blocks falls to every node; you are correct there (and I never claimed otherwise). But, if a miner produces a block that the vast majority of nodes reject, then the network effectively splits into two parts -- one part where the block was never "seen" and the other part where it was. If the part that never "sees" the block represents more economic activity -- e.g. the majority of exchanges' nodes, the majority of wallets' nodes, etc. -- then it doesn't matter how much mining PoW gets sunk into that block and its descendants because they will never be processed. Downstream, that means that the miner's coins never materialize on these nodes, which makes mining non-relayed blocks unprofitable. Miners need other nodes to recognize their blocks in order for those other nodes' operators to recognize the existence of their coins. For example, consider what would happen if a miner produced a block that tried to spend a Segwit output without consideration of the witness. Under the Bitcoin protocol, this is technically allowed -- a Segwit output looks like an anyone-can-spend output. But due to the extra Segwit rules, only pre-Segwit nodes would accept and relay this block. Considering that nearly all exchanges, wallets, custodians, etc. apply the Segwit rules, this would mean that this block would be treated as invalid and its coinbase rendered effectively unspendable. Even if 100% of the Bitcoin miners tried to build on top of this Bitcoin-valid but Segwit-invalid block, all their blocks would be similarly rejected. Only pre-Segwit Bitcoin nodes would accept these blocks, but hardly anyone runs them [1] (note that Segwit support first appeared in version 0.16; there are indeed still some people running pre-Segwit nodes). [1] https://luke.dashjr.org/programs/bitcoin/files/charts/softwa... |
|
Also you are linking to a person who thinks the sun revolves around the earth and that there is nothing wrong with slavery because the bible says so.