# Difference between full node and bootstrap nodes in Ethereum?

I know that when a new geth instance runs it connects to the bootstrap nodes. What I want to know that do other nodes download blockchain from the bootstrap nodes or nor? Bootstrap nodes are highly available so why just simply connect to bootstrap nodes instead of connecting to some other node in the network.

What if bootstrap nodes provide wrong information. The whole network is compromised right?

How is a regular node different than a bootstrap node? And also How does peer discovery actually works? What if nodes only download and not upload? What if I execute a denial of service attack which connect to many nodes in the network and downloads blockchain?

• You may ask only one question at a time to help people answer without being off topic 😉 – Nicolas Massart Oct 1 '16 at 8:51

Q: I know that when a new geth instance runs it connects to the bootstrap nodes. What I want to know that do other nodes download blockchain from the bootstrap nodes or nor?

A: No. Regular nodes do not download the blockchain from bootnodes. The only role for the bootnodes is to allow regular nodes to connect to and get the connection information on other regular nodes. The regular nodes will then use this information to connect to other regular nodes.

Q: Bootstrap nodes are highly available so why just simply connect to bootstrap nodes instead of connecting to some other node in the network.

A: The bootnode's only role is to provide the connection information for regular nodes to connect to each other. The connection information for several bootnodes are hard-coded into the regular node source code - see bootnodes.go

As the bootnodes only serve very little information to each regular node, the bootnode server resources can be focussed on providing this information and not get bogged down transferring the blockchain data.

Q What if bootstrap nodes provide wrong information. The whole network is compromised right?

A Not necessarily. You are able to specify new bootnodes on the command line parameters of the regular node client:

geth help | grep bootnode
--bootnodes value   Comma separated enode URLs for P2P discovery bootstrap


You are also able to manually enter a list of other regular nodes on the network using the admin.addPeer(...) command.

Recently many users reported that their regular nodes was not able to find peers. There were some problems with the bootnodes. See geth does not sync out of the box.

The temporary workaround was to get a list of regular node connection information from peers that were already connected to peers, and pasting this connection information into the regular node that was experiencing the peer discovery problem. See How can I create a list of peers from my syncing geth node to manually paste into my non-syncing geth node using the admin.addPeer() command?.

Q: How is a regular node different than a bootstrap node?

A The regular node has the peer discovery mechanism of the bootstrap node. Additionally, the regular node will download and synchronise the blockchain with other regular nodes. The bootstrap node cannot be used directly to synchronise the blockchain.

Q: And also How does peer discovery actually works?

• Could you move your comment into a new question please. The answer is not short. Is there any particular reason why you want to use a bootnode? For a private network? You can use static nodes and/or trusted nodes, which can be full geth nodes. – Bokky WeAreAllAssange PooBah Oct 1 '16 at 12:39