Quote from: ocminer on December 01, 2016, 10:24:08 AM

What do you mean by "protecting a pool" ? I'm running pools for years and I know very well how to "protect" them, or was anything hacked ? He forked off and banned the node(s) of my pool three times, invalidating blocks on the pool even while the pool had a lot more than 50 % of the network.

He was claiming the pool's p2p node was "open" - well.. A p2p port is designed to be open, isn't it ?

The RPC port is the port which needs to be protected and XVC doesn't even have password authentication for the RPC port neither does it have host-based access restrictions.. Every bitcoin based wallet has that since the very first version.. (rpcallowip... rpcusername/password etc) ... So the only way of protecting a XVC wallet is by making it listen on 127.0.0.1 only and having iptables rules in place.

Good point, this is a complicated part of the coin, specially the fact that it's stated several times throughout the instructions not to open the RPC port.
The thing is that this, in itself, shows John the bad actors.

Hope he being out is just him dealing with this bug to avoid these absurd claims. The RPC port being closed, it is protected.
This rule is probably there because of other parts of the coin, such as chainblender.

mrsky

Posts

Merits