Post
Topic
Board Bitcoin Discussion
Re: Why Bitcoin Core Developers won't compromise
by
dinofelis
on 18/05/2017, 16:46:55 UTC
Full nodes undertake a "UASF" and only accept blocks from the miners that are signaling for segwit and thus bring about a fork.

Well, then these nodes will stop if the block chain has a single block on it not signalling segwit.
That's based on the assumption that at least some of the miners that are currently signaling for segwit would not "switch" (at some point at least)  to build the "segwit" blockchain.

?

The current chain is a succession of blocks that are signalling and not signalling Segwit.   All miners are still building the same block chain, one block on top of the other, some with a segwit signal, others without.  

For instance,
480 000 SW
480 001 SW
480 002 no SW
480 003 no SW
480 004 SW
480 005 SW
etc...

If you run a non-mining node that considers non-SW blocks as invalid, starting from 480 000, then that node will:

accept 480 000 (it is a SW block)
accept 480 001 (it is a SW block)

refuse 480 002: it is a non-SW block.

So it will wait until it finds a SUCCESSOR to block 480 001, but with SW signalling.

That block will never come.

Block 480 004 is the first SW block that comes along, but is not a successor to 480 001.  So it is rejected.  And all others following are rejected, because they are not a successor to 480 001.

The node stops.

That's about it.

When the unique chain is at 497 807, your node is still waiting for the block 480 001 with SW signalling.