Please feel free to edit this question for any fix or enhancement.
Your contribution is valuable especially that EOS and its resources
are frequently updated and this answer will need to be updated
The front-end can be configured as a set of non-producing nodes to serve as a cluster. Those nodes should be the ones ...
Both net_plugin and bnet_plugin are responsible of to the Peer-to-Peer network. The P2P network is the network that is between the Block Producers.
However, net_plugin is the old plugin for the P2P network. Whereas, the bnet_plugin is a newer and optional protocol plugin that works side-by-side with the existing net_plugin. But, a bnet_plugin only ...
In DPoS there are turnwise block creations of every of the (in EOS) 21 block producers. Therefore orphan or stale blocks which are common in PoW chains, do not usually occure. Any misbehaving block producer should theoretically be voted out.
The white paper concludes:
Under normal conditions a DPOS blockchain does not experience any forks because, rather ...
The option appears to have been introduced in v1.0.4, and it enables low-water marks for socket communication to minimise the number of send calls required to get a minimum number of bytes (i.e. enable faster communication.) However, this is not widely supported; poll(2) in Linux ignores SO_RCVLOWAT, but OS X may support it.
In the EOSIO ecosystem, the CPU, RAM, and NET are all provided to the chain by the block producers.
The EOS tokens gives you access to the staking resources (CPU & NET = Bandwidth) which are replenished after an amount of time and then there is RAM (on-chain storage). Keep in mind that developers have to purchase enough RAM to run a smart contract.
Looks like you're trying to run a single node test net.
Try not to confuse it with the main net as that's the popular EOSIO based Blockchain with Block Producers like EOS New York or Genereos.
To start your own single node test net you're best off reading the docs found here at https://developers.eos.io/eosio-nodeos/docs/ I highly recommend using the ...
Add the following entry to config.ini.
p2p-peer-address = mainnet.eoscalgary.io:80
You can see a number of configuration examples at the link below.
You can see the url address of the mainnet and BP at the link below.
The EOS software doesn't define or require any the network architecture, that is completely decided by launch implementations. The current proposal for the mainnet EOS chain (being engineered and launched as I write this) will be based on a p2p topology with a mesh component. It's possible in the future there can be other network architectures for this ...