<p>1) None. Don't open the port (default).</p>

<p>2) None required. 
Obviously you don't want to download Bitcoin Core binary from random sites, you want validate it, etc. as per bitcoincore.org's instructions.</p>

CC BY-SA 3.0
2017-11-20T07:32:19.747Z
2017-11-20T07:32:19.747Z
whatever
<p>What are the security risks posed by running a full node bitcoin core client? On a typical system, port 8333 is open and all other nodes can actually 'see' my machine and sites like <a href="https://bitnodes.earn.com/" rel="nofollow noreferrer">https://bitnodes.earn.com/</a> can verify the connection. </p>

<p>How can the risks be mitigated? (I'm on Windows)</p>

CC BY-SA 3.0
2017-11-20T08:59:02.337Z
The risk of running a full node (as opposed to using different wallet software/service), or the risk of opening up a port (as opposed to leaving it closed, but still running Bitcoin Core)?
Pieter Wuille
<bitcoin-core><security><full-node><wallet-security>
Security risk(s) in running bitcoin core full node
Regmi
# Security risk(s) in running bitcoin core full node

(Asked by: username_0 on 2017-11-19)

What are the security risks posed by running a full node bitcoin core client? On a typical system, port 8333 is open and all other nodes can actually 'see' my machine and sites like <https://bitnodes.earn.com/> can verify the connection.

How can the risks be mitigated? (I'm on Windows)

**Tags:** bitcoin-core, security, full-node, wallet-security

> **Comments:**
> **username_1**: The risk of running a full node (as opposed to using different wallet software/service), or the risk of opening up a port (as opposed to leaving it closed, but still running Bitcoin Core)?  

---

## 1 answers

### Answer by username_2 on 2017-11-20. Score: 2

1) None. Don't open the port (default).

2) None required.
Obviously you don't want to download Bitcoin Core binary from random sites, you want validate it, etc. as per bitcoincore.org's instructions.


---

