<p>All peers are treated equally when relaying chain-extending blocks (as James C. stated in a comment on another answer). The node will announce the block to <strong>all of its peers</strong> and since that block was just found, all of the peers should request the new block.</p>
<p>Many miners will also announce new blocks on <a href="https://bitcoinfibre.org/" rel="nofollow noreferrer">Fast Internet Bitcoin Relay Engine (FIBRE)</a> in addition. Any new block on FIBRE will be immediately broadcast to all participants in a compressed format based on compact blocks (BIP152).</p>

CC BY-SA 4.0
2020-08-25T17:20:35.660Z
2020-08-25T17:28:35.740Z
2020-08-25T17:28:35.740Z
Murch
<p>The number of peers connected to your node is configurable. You can increase it from 8. Your node will broadcast to the connected peers, who, in turn, will broadcast to their connected peers.</p>

CC BY-SA 4.0
2018-11-25T12:54:22.513Z
For each node, up to 8 nodes can be actively connected and 117 foreign connections can be accepted. So is the broadcast block broadcast to 125 nodes or just to the actively established nodes?
and zhao
CC BY-SA 4.0
2018-11-30T07:58:28.857Z
You can configure inbound, outbound and permanent connections for your node. I am not sure what 117 refers to, inbound? Outbound connections are also foreign as their addresses are discovered on the network(not permanent). In any case, you can set the limits there. All connections are treated equally in respect to broadcasting, propagating of chain-extending blocks.
James C.
CC BY-SA 4.0
2020-08-25T08:27:48.040Z
This is no longer true. Blocks are no longer sent unsolicited.
David Schwartz
CC BY-SA 4.0
2018-11-25T07:56:10.080Z
2018-11-25T07:56:10.080Z
user1202278
<p>In the Bitcoin network, when a miner discovers a new block, he needs to broadcast it to other nodes. Does the node only broadcast to outbound connections or does it broadcast to inbound connections as well? I hope to get the result according to the source code and it would be great if the answer would point out the file of the corresponding code.</p>

<connection><broadcast>
Which peers does a node broadcast a new block to?
and zhao
# Which peers does a node broadcast a new block to?

(Asked by: username_0 on 2018-11-24)

In the Bitcoin network, when a miner discovers a new block, he needs to broadcast it to other nodes. Does the node only broadcast to outbound connections or does it broadcast to inbound connections as well? I hope to get the result according to the source code and it would be great if the answer would point out the file of the corresponding code.

**Tags:** connection, broadcast


---

## 2 answers

### Answer by username_1 on 2020-08-25. Score: 1

All peers are treated equally when relaying chain-extending blocks (as username_3 C. stated in a comment on another answer). The node will announce the block to **all of its peers** and since that block was just found, all of the peers should request the new block.

Many miners will also announce new blocks on [Fast Internet Bitcoin Relay Engine (FIBRE)](https://bitcoinfibre.org/) in addition. Any new block on FIBRE will be immediately broadcast to all participants in a compressed format based on compact blocks (BIP152).


---

### Answer by username_2 on 2018-11-25. Score: 0

The number of peers connected to your node is configurable. You can increase it from 8. Your node will broadcast to the connected peers, who, in turn, will broadcast to their connected peers.

> **Comments:**
> **username_0**: For each node, up to 8 nodes can be actively connected and 117 foreign connections can be accepted. So is the broadcast block broadcast to 125 nodes or just to the actively established nodes?  
> **username_3**: You can configure inbound, outbound and permanent connections for your node. I am not sure what 117 refers to, inbound? Outbound connections are also foreign as their addresses are discovered on the network(not permanent). In any case, you can set the limits there. All connections are treated equally in respect to broadcasting, propagating of chain-extending blocks.  
> **username_4**: This is no longer true. Blocks are no longer sent unsolicited.  

---

