user111740: I see that bitcoin-cli can do getpeerinfo. However, it typically returns around 30 different IPs. Even if I ask for only outbound ones, I get around 16 addresses.
$ bitcoin-cli getpeerinfo | grep "inbound\": false" | wc -l
16

How do I narrow down to those 8 that will be used to propagate the next block my node gets to propagate?

user208: Bitcoin Core nodes propagate blocks and transactions to all their peers, not just outbound ones.
And if you have 16 peers that getpeerinfo reports "inbound": false for, then all 16 are outbound connections. Presumably you're using addnode functionality, or using modified source code, as Bitcoin Core itself will not make more than 10 automatic outbound connections, but for manual connections (addnode) there is a separate limit.

111740: <p>I see that <code>bitcoin-cli</code> can do <code>getpeerinfo</code>. However, it typically returns around 30 different IPs. Even if I ask for only outbound ones, I get around 16 addresses.</p>
<pre><code>$ bitcoin-cli getpeerinfo | grep &quot;inbound\&quot;: false&quot; | wc -l
16
</code></pre>
<p>How do I narrow down to those 8 that will be used to propagate the next block my node gets to propagate?</p>
 208: <p>Bitcoin Core nodes propagate blocks and transactions to <em>all</em> their peers, not just outbound ones.</p>
<p>And if you have 16 peers that <code>getpeerinfo</code> reports <code>&quot;inbound&quot;: false</code> for, then all 16 are outbound connections. Presumably you're using <code>addnode</code> functionality, or using modified source code, as Bitcoin Core itself will not make more than 10 automatic outbound connections, but for manual connections (addnode) there is a separate limit.</p>
