pull down to refresh
Note: it's not that the node isn't configured as listening, it's that most people don't have their routers port forwarding TCP/8333 to their node. There is a security risk in doing this, that can be addressed by adding another router.
reply
It's really easy to run a non listening node. All the defaults push toward this (as far as I understand).
reply
reply
Ah! I wondered if I had that wrong. I'm not sure why I had the idea that default behavior was not accepting inbound connections.
reply
It's not that the node isn't listening, it's that it's behind a NAT router that is not port forwarding TCP/8333 to the node and allowing inbound connections.
reply
A major contributing factor to the vulnerability is how few nodes are IPv4 reachable. That is something that individual node runners can help solve immediately.