Quote from: kalisto on December 01, 2016, 12:19:35 AM

Quote from: ocminer on November 30, 2016, 11:44:41 PM

Quote from: hankrules on November 30, 2016, 11:08:17 PM

How about just create a new genesis block and call it chocolatecoin?

Won't work, all his backdoors / tricks are still in the code - the code can't be trusted in its current state.

lol you are fast.. lurking in slack? if you cannot protect your pool dont come here bashing with fud like a ctr shill Grin

if you can point us to 1 backdoor you can earn some respect back

Oh sorry I missed who you are

Obviously he was able to fork off pools/miners from "his" chain without even having more than 51% of the network, if that is not evidence enough.. Well..
And no, it wasn't only my pool

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.