Quote from: dinofelis on March 09, 2017, 09:31:57 PM

Of course, because the A chain is NOT ANY LONGER. So A "being stuck at 460001" is perfectly normal,

your getting it

Quote from: dinofelis on March 09, 2017, 09:31:57 PM

it is the longest chain that is in agreement with A's protocol.

and now you lost yourself again.
A is not the longest chain.. u just said it yourself its not.. just one sentance prior.
the only way for 460001a to be the longest chain.. is to not see any peers with 460003b.. which involves .... BANNING B nodes

Quote from: dinofelis on March 09, 2017, 09:31:57 PM

Quote from: franky1

but the B nodes keep growing.
no way would B drop 460003 to go back to 460001
if B accept and happy with 460002B1 460003b2

Of course.

Quote from: franky1

A stuck at 460001

Because that was the longest A chain up to that point.

only if A has banned B

Quote from: dinofelis on March 09, 2017, 09:31:57 PM

But now, an A-miner has released a second A block, built upon 460001 (because that miner, too, has an A node that has as a longest chain, the one with 460001, and has mined a block on top of it).

only if A has banned B
other wise A sees 460002A and 460003B and still sees 460003B as the highest height and keeps requesting what B has as they have the heighest height.
again resulting in orphans and being stuck even if 460002a exists.
still requesting 460003 because it can see 460003

Quote from: dinofelis on March 09, 2017, 09:31:57 PM

That A-miner now broadcasts his block 460002A2. This is relayed by all A-type nodes. When your "stuck" A-type node receives this block, he accepts it, and is now at 460002A2, *like he should* because that's now the longest A-compatible chain.

unless banning B... 460002A2 is not the longest chain.

i think i am getting where your missing something.
a node doesnt know the contents of a block until it receives it and checks it.

your thinking A sees that 640003 is bad before even downloading it.
sorry but it has to download it to see what it is.

meaning every time it scans the network all it sees is 640003 is highest.
without knowing if its a 640003a or a 640003b unless it requests it to see what it is..

again to avoid getting 640003b it has to ban nodes holding 640003b

Quote from: dinofelis on March 09, 2017, 09:31:57 PM

Quote from: franky1

A then has to decide to:
continue in orphan hell of rejecting B
stay stalled by just turn node off
upgrade and join B
or ban B to not see 460003 and instead able to build on A

Well, of course, he will do the last thing, and take block 460002A2 when it becomes available. Nothing difficult.
That the A-node, with its longest chain up to 460001A1

A is only longest if A is all it sees... by banning B nodes

Quote from: dinofelis on March 09, 2017, 09:31:57 PM

was "wasting its time checking B blocks" is not a problem, it HAD the longest possible chain for him at that point. When it receives the next A block, it adds it. As it should.

Quote from: dinofelis on March 09, 2017, 09:31:57 PM

No "orphan drama".
A nodes build the A chain. BU nodes build the B chain.

when it bans B nodes