Timeline for How Are Transactions/Blocks Broadcasted
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 4, 2018 at 0:06 | comment | added | Nicholas | I learned through other research that the peers are discovered through Kadelima. So Kadelima is used to broadcast blocks too? How specifically does that modified version work (there must be some edit, because it would not be efficient to just lookup every node in the network in order to distribute a block). | |
| Jun 29, 2018 at 14:55 | comment | added | conwise17 | What happens is when a machine downloads the go-ethereum software, then it becomes a node, and connects to other nodes nearby through accessing to the network instance which is usually something like instance=Geth/v1.8.2-stable/darwin-amd64/go1.10 once connected, if the node sends a transaction it is broadcasted across the server, the transaction is sent to the peers which the said node is connected to first (MAX IS USUALLY 25), then to the peers of the peers that received the transaction first and so on. The same propagation happens with blocks in the network. | |
| Jun 28, 2018 at 11:41 | comment | added | Nicholas | I honestly don’t know what you mean. I understand the blockchain very well, I just want to understand the peer to peer aspect. There has to be some way that transactions are sent to miners and blocks are sent to all nodes, because a ‘blockchain’ isn’t some ephermeal thing that does that all for you. It’s just a data structure, and without some way of connecting to other peers, there is no decentralization, value, network, etc. | |
| Jun 28, 2018 at 5:54 | history | answered | conwise17 | CC BY-SA 4.0 |