But of course not. For the old nodes, B1 and B2 are simply invalid blocks. So their height is at 460001. If I send an invalid block to another node, I suppose he's simply going to reject it, no ?
LOL
A see it as invalid. but then they look over the network and see others have 460,003 so request it. then realise its B2 again.. and reject it
and then
A see it as invalid. but then they look over the network and see others have 460,003 so request it. then realise its B2 again.. and reject it
and then
A see it as invalid. but then they look over the network and see others have 460,003 so request it. then realise its B2 again.. and reject it
and then
A see it as invalid. but then they look over the network and see others have 460,003 so request it. then realise its B2 again.. and reject it
and then
A see it as invalid. but then they look over the network and see others have 460,003 so request it. then realise its B2 again.. and reject it
and then
A see it as invalid. but then they look over the network and see others have 460,003 so request it. then realise its B2 again.. and reject it
thus not syncing and A being stuck at 46000A1..
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 they continue with it
A stuck at 460001
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
Otherwise, I can bring down the whole bitcoin network by making 5000 successive bogus invalid blocks with erroneous hashes (not difficult) and tell the whole bitcoin network that we are 5000 blocks ahead ? Everything comes to a grinding halt with such a simple attack ?
now your just making up fairy tales. because they would just not be accepted either.. nothing to do with height. but about not meeting rules.
Of course not. B1 and B2 are simply considered invalid blocks by old nodes.
invalid to A which leaves A stuck (B accepts them so B continues)
The old nodes will all agree that they are at height 460001.
no old nodes will see its peers are at 460003. and keep trying to get it to sync to it. but then reject what it gets to be left at 460001a
leading to sync issues.
forcing the user to decide.
join B(upgrading software)
be a numbskull just remaining unsynced requesting and rejecting
ban B to grow A because if A grew A without a ban if A made 460002.. the nodes will still be looking to grab 460003B and rejecting 460002A
And those nodes receiving blocks B1 and B2 will reject them, and not even propagate them. But all BU nodes will accept them, propagate them, and their counter will be at 460003.
now your getting it
An old node asking a BU node to send him the blocks, will conclude that this node is "confused". Otherwise, I can bring down the whole bitcoin network with one single "confused" node 5000 fake blocks in the future.
Period.
now your getting it.
leading to sync issues for A.
forcing the user to decide.
join B(upgrading software)
be a numbskull just remaining unsynced requesting and rejecting
ban B to grow A