Topic: Some questions about Nakamoto consensus. (Read 253 times)

True, I already heard a few times that the number seems to be much smaller than the actual network size, apparently. But it's hard to crawl reliably; amongst other factors also since many nodes are e.g. just accessible via Tor and such. However, this is somewhat by design.

The methodology that Bitnodes used to find and determine Bitcoin nodes is inaccurate. The crawler essentially asks the nodes for their version and waits for a response and then subsequently requests for the other peers as well. This doesn't provide an accurate representation of the network as a whole. In fact, there is no way to actually accurately determine the node size.

They aren't connected to each other, they are listening nodes that can accept incoming connections and "talk" to any node that instantiates the connection. What we don't know is which nodes are connected to which nodes which seems to be what @YYBNN wants to see.
BTW many of the IP addresses listed on bitnodes.io specially in first pages are fake/spy nodes.

I suspect the ones on bitnodes are all connected and talking, since the site's probing nodes won't accept misbehaving nodes as 'valid' and won't add those to the graph / data.

Got it, they get isolated in P2P network because honest guys won't talk to them. Maybe there are papers in research level, but it would be interesting to visually see them as a network like nodes and minders are points and they are connected by an edge if they talk each other. I think dishonest guy would be disconnected. There is https://bitnodes.io/ which has some info, but I don't think it has data about if they are connected like they are talking. Are there such data so one can analyze?

 

You are describing any of the many bitcoin "fork" coins out there (Bitcoin Cash, Bitcoin SV, Bitocin Gold, etc).  In each of these instances a group decided to create blocks that are invalid according to Bitcoin.  They all decided to run nodes that would accept these invalid blocks, and to run miners that would mine these invalid blocks.  The result is a chain split where some nodes follow the new rules and are therefore on a forked network with a forked chain, and others continue to follow the old rules and are still on the old network with a completely separate chain of blocks.

That's exactly what happens any time any group would try to accomplish this, regardless of whether they have 5 nodes and miners or 5 billion nodes and miners. Their blocks are accepted by those that are running their software, and are ignored by anyone not running their software.

Even if they don't stop on that block, but continue adding either more invalid or the incoming new legit blocks (even though the previous block hash won't match - they're not following the rules anyway), it will result in two separate, not inter-communicating networks. The legit Bitcoin network and the fake Bitcoin network which has one or more invalid blocks.

Since nobody will talk / connect to the fake network, nobody will be harmed by it; hence it's not really an attack altogether.

The important thing to note is that nodes that disagree simply stop talking to each other. Even if some malicious actor adds 100,000 "bad" nodes to the network, the 15,000 "good" nodes (and miners) will just ignore them and continue on. An eclipse attack (where the good nodes have trouble finding other good nodes) as @ranochigo mentioned is a possibility, but it would still not be fatal to the network.

If you propagate an invalid block, then your node would just be disconnected and added to the ban list of each node. This makes sure that only the malicious block of nodes are segregated from the others but not the honest nodes. This doesn't actually affect the rest of the network as they would just wait to get an honest peer which doesn't propagate invalid blocks.

It is perfectly possible to execute a Sybil attack against the network, and the attack that can happen would be an eclipse attack. However, Core has countermeasures against it as well.

You mean "Bitcoin" consensus.

That's correct.
Miners nowadays connect to a pool that is running a node and builds the blocks, so multiple miners connected to a pool are mining the same block.

It doesn't matter what others do; when you are running a full node you rely on your own verification so there is no "risk" here.
The only negative thing about large number of malicious nodes is them wasting your time to verify an invalid block, reject it and ban them.

They can not break anything. If they accept invalid blocks they essentially isolate themselves since they stop on that block and can't build on it while the rest of the network keeps on building on the correct chain.

Just like mempool, every node has its own blockchain (the ledger) and nobody else can mess it up for them.

It is an attack but it is a pointless one since it can not achieve anything or be sustained.

It might be bit too elementary to ask here, but let me ask some questions. I am learning about Bitcoin. Currently, I’m learning about distributed consensus on chapter 10 of mastering Bitcoin by Andreas Antonopoulos.

As far as I read, you can summarize this with 3 parts for Nakamoto consensus. The first is for full nodes to validate transactions. They make sure conditions including AcceptToMemoryPool, CheckTransaction, and CheckInputs in Bitcoin Core. Once transactions are ok, each node put them into a transaction pool.

Then, miners make a candidate block and do mining. (I think every node is independent, so transaction pool is slightly different among nodes so each miner mines a block consisting of different transactions, but mostly likely with the same previous block hash on the longest chain. I hope I'm getting it right.)

Once a block is mined by some miner, the miner propagates to its neighbor nodes, and each node checks. If a block is correctly mined satisfying conditions like CheckBlock and CheckBlockHeader in Bitcoin core, they put it on the ledger, and propagate and other nodes also check it if they haven't yet.

To fully understand, I should probably need to run a node and see, but I’m thinking about the risk of a majority of full nodes not doing jobs right. The first and the last step where full nodes validate, they could simply validate an invalid block to be valid and propagate to its neighbors. And, I totally understand an argument like other nodes will not validate and won’t talk to that bad node. However, we never know that if some malicious groups trying to break Bitcoin’s consensus system especially because it doesn’t cost a lot to be a full node.  To get 51% of hash rate is very expensive, but say you make so many bad full nodes and trying to mess up the ledger sounds reasonable.. Like run 100000 nodes and validate poorly. (Quick search shows 15000nodes currently)

Now, if so many nodes are bad, then miners will stop talking to them and only good nodes will hear new blocks, but my point is that the health of the network is not obvious. Therefore, some attacks could be possible here, what's making it not to be attacked? (Miners also can lie, but if their blocks get rejected, they lose money. Nodes try to be honest if they make transactions themselves to make sure their transactions went ok, so some incentives for nodes to act well.)