<p>If your node initiated the connection, it's outbound, otherwise it's inbound. Nodes will send and receive data from both types of connections exactly the same way.</p>

<p><code>maxconnections</code> sets a limit on the total number of connections, so if you set it to eight, your node will probably initiate connections to other eight nodes before any node can initiate a connection to it.</p>

<p>Keep in mind that according to <a href="https://bitcointalk.org/index.php?topic=855538.0" rel="noreferrer">this forum post</a>, each open connection will take only a few kilobytes of RAM, so reducing the number of connections might not save all that much of memory.</p>

<p><strong>EDIT</strong>: By running a full node that has no slots for incoming connections, you act as a leecher, and you do more bad than good for the Bitcoin network, as <a href="https://www.reddit.com/r/Bitcoin/comments/1scd4z/im_running_a_full_node_and_so_should_you/cdw3lrh?context=3" rel="noreferrer">Gavin Andresen said on Reddit</a>. You would help the network if you allowed a few inbound connections. As discussed earlier, that's unlikely to take up any significant amount of RAM.</p>

CC BY-SA 3.0
2016-01-25T14:59:56.863Z
`By running a full node, you still help the network, even if your node has no slot for incoming connections.` How? If nothing is using you're node as a trusted source of data, you're just relaying blocks and transactions. More peers, however, means more hops and more validation, which means slower propagation times for both transactions and blocks.
morsecoder
CC BY-SA 3.0
2016-01-25T17:42:24.550Z
@StephenM347 you are correct. I did some extra research and confirmed what you said. Edited the answer, thanks.
Wladston Ferreira Filho
CC BY-SA 4.0
2019-06-03T01:07:43.683Z
Why would you automatically be a leecher just because you don't accept inbound connections? Don't honest full nodes send and receive data regardless of who made the connection (outbound or inbound)?
B T
CC BY-SA 3.0
2016-01-24T18:38:16.190Z
2016-01-25T17:41:38.510Z
2016-01-25T17:41:38.510Z
Wladston Ferreira Filho
<p>I have port 8333 open with 8 outbound and 2 inbound connections.</p>

<p>Is my node transmitting and receiving transactions and blocks from both types of connections? Or does the "inbound" flag mean I am just downloading from that peer, and not sending any information back?</p>

<p>If, for the sake of saving RAM, I set <code>maxconnections</code> to 8, will they all be outbound? Even if port 8333 is open? In this configuration, is my node still "helping" the network?</p>

CC BY-SA 3.0
2016-01-12T01:08:41.337Z
To the best of my understanding: Inbound means the remote peer initiated the connection to you. Outbound means you made the connection to a remote peer. This is just diagnostic info and doesn't affect behavior. Transactions and blocks can flow in both directions with any peer - unless the peer has the [relay bit](https://en.bitcoin.it/wiki/Protocol_documentation#version) set to off.
Nayuki
CC BY-SA 3.0
2016-01-12T19:12:08.043Z
@NayukiMinase: Feel free to post that as an answer! :)
Murch
CC BY-SA 3.0
2016-01-13T04:22:57.910Z
I feel that what I wrote doesn't provide objective evidence to support the statements, and I haven't answered all parts of the OP's question...
Nayuki
<peers><connection>
What is the difference between inbound and outbound connections?
pinhead
# What is the difference between inbound and outbound connections?

(Asked by: username_0 on 2016-01-11)

I have port 8333 open with 8 outbound and 2 inbound connections.

Is my node transmitting and receiving transactions and blocks from both types of connections? Or does the "inbound" flag mean I am just downloading from that peer, and not sending any information back?

If, for the sake of saving RAM, I set `maxconnections` to 8, will they all be outbound? Even if port 8333 is open? In this configuration, is my node still "helping" the network?

**Tags:** peers, connection

> **Comments:**
> **username_1**: To the best of my understanding: Inbound means the remote peer initiated the connection to you. Outbound means you made the connection to a remote peer. This is just diagnostic info and doesn't affect behavior. Transactions and blocks can flow in both directions with any peer - unless the peer has the [relay bit](https://en.bitcoin.it/wiki/Protocol_documentation#version) set to off.  
> **username_2**: @username_1Minase: Feel free to post that as an answer! :)  
> **username_1**: I feel that what I wrote doesn't provide objective evidence to support the statements, and I haven't answered all parts of the OP's question...  

---

## 1 answers

### Answer by username_3 on 2016-01-24. Score: 6 | Accepted answer

If your node initiated the connection, it's outbound, otherwise it's inbound. Nodes will send and receive data from both types of connections exactly the same way.

`maxconnections` sets a limit on the total number of connections, so if you set it to eight, your node will probably initiate connections to other eight nodes before any node can initiate a connection to it.

Keep in mind that according to [this forum post](https://bitcointalk.org/index.php?topic=855538.0), each open connection will take only a few kilobytes of RAM, so reducing the number of connections might not save all that much of memory.

**EDIT**: By running a full node that has no slots for incoming connections, you act as a leecher, and you do more bad than good for the Bitcoin network, as [Gavin Andresen said on Reddit](https://www.reddit.com/r/Bitcoin/comments/1scd4z/im_running_a_full_node_and_so_should_you/cdw3lrh?context=3). You would help the network if you allowed a few inbound connections. As discussed earlier, that's unlikely to take up any significant amount of RAM.

> **Comments:**
> **username_4**: `By running a full node, you still help the network, even if your node has no slot for incoming connections.` How? If nothing is using you're node as a trusted source of data, you're just relaying blocks and transactions. More peers, however, means more hops and more validation, which means slower propagation times for both transactions and blocks.  
> **username_3**: @StephenM347 you are correct. I did some extra research and confirmed what you said. Edited the answer, thanks.  
> **username_5**: Why would you automatically be a leecher just because you don't accept inbound connections? Don't honest full nodes send and receive data regardless of who made the connection (outbound or inbound)?  

---

