Outbound Connection Slots

Outbound connection slots are the peer links a Bitcoin Core node initiates itself, as opposed to inbound connections it merely accepts from the network. By default a node opens eleven such slots, and the distinction is the backbone of Bitcoin's peer-to-peer security model: outbound peers are ones you chose from your own address database, so they are far harder for an attacker to control than inbound peers, which anyone on the internet can offer you for free.

The default breakdown

The eleven outbound slots are divided by role. Eight are full-relay connections that exchange transactions, peer addresses, and blocks — the ordinary working links that keep your mempool and chain tip current. Two are block-relay-only connections that relay blocks and nothing else: no transactions, no address gossip. Because they carry no transaction traffic, they are invisible to the network-graph inference techniques researchers and adversaries use to map which nodes connect to which, making them a hidden lifeline for consensus-critical data. The eleventh slot hosts a short-lived feeler connection that periodically dials an address from the "new" table, verifies it actually speaks the protocol, promotes it to the "tried" table, and disconnects. Feelers keep the address database honest so that future outbound choices are drawn from peers known to be real.

Why the split matters for attack resistance

The layout is a deliberate defense-in-depth design against eclipse attacks, in which an adversary tries to monopolize all of a victim's connections and feed it a false view of the chain. Because the block-relay-only slots do not appear in the public gossip graph, an attacker cannot even enumerate the full set of links it would need to capture. Because the feeler continuously refreshes verified addresses, poisoning the address database with attacker-controlled entries becomes a moving target. And Bitcoin Core deliberately diversifies outbound peers across network groups and, more recently, across distinct transports — IPv4, IPv6, Tor, I2P, CJDNS — so the full-relay slots do not all traverse one autonomous system that a single well-placed adversary could dominate. Add anchor connections, which remember two block-relay-only peers across restarts, and a rebooting node cannot be trivially captured during its vulnerable reconnection window. The result: isolating a node means simultaneously controlling several independent, partly invisible, deliberately diverse channels — a dramatically harder job than filling its inbound slots.

What a node operator should take from this

For the home node runner, the practical lessons are modest but real. First, outbound security works without port forwarding: a node behind NAT that accepts no inbound connections still gets the full protection of its eleven chosen links, so "unreachable" nodes are not second-class citizens for their own security. Second, resist the urge to over-configure. Manually pinning all your connections to a handful of "trusted" peers with -connect replaces a diversified, partly hidden peer set with a static, enumerable one — usually a downgrade. Third, enabling additional networks like Tor alongside clearnet genuinely strengthens the diversity the design counts on. A miner should care too: a mining operation whose node is eclipsed can be fed stale work or have its blocks withheld from the honest network, converting connection-layer weakness directly into lost revenue.

The numbers themselves are worth memorizing because they anchor so much other behavior: 8 full-relay plus 2 block-relay-only plus 1 feeler gives the canonical 11, while the default cap of 125 total connections means a reachable node offers over a hundred inbound slots to the network. Running a reachable node is therefore a public good — every listening node adds inbound capacity that lets new and NAT-bound nodes find the honest network at all.

The outbound slot layout ties directly into eclipse-attack resistance and is mirrored on the inbound side by peer eviction logic, which decides who gets displaced when strangers compete for your attention. Together they are a quiet example of Bitcoin's engineering culture: no trusted authority, just carefully rationed trust in peers you picked yourself.