[ANN] The XVC take over! ICO. Collect BTC for expensive devs.

[ocminer]

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

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

Hey your Bitcointalk account is exposed to the public. Your account is vulnerable. I will ask the mods to ban your account.

This is how stupid John his theory sounded when he said suprnova is not safe.

To mine, a pool need to have open ports.. Otherwise you can't connect.

He had nothing to back up with except bluffing /lying.
But maybe you are a pro network engineer and be able show everyone a detailed security analysis.

If you dont close your inbound tcp ports for the daemon you are not qualified to run a pool lol.

Stratum is the only port that should be open to the public and talks internal to the daemon.

Crybabies

Lol and the daemon talks to itself because it isn't allowed to communicate with other peers, right?

You have p2p ports and rpc ports.  Of course close the rpc port but p2p is the port which connects to other daemons, other wallets...

Drunk?

LOL i get it, you dont know how a firewall works.
You dont want external peers connecting to your node, you submit your work to the network.
Only outbound is important so you get a firewalled peer, how else does the BTC client work behind a router with closed ports? ROFLOL

Are you really that stupid? 

LOL, I see a real network expert here




Of course you want external nodes connecting to your node, this will propagate your blocks faster, especialy when you're a pool. You always want as much connections as possible, your're not a peer, you're a pool.. If you're not connecting well, your Blocks won't propagate fast and you'll have problems with orphans. Thats also the reason why there's always a main and a backup node, one gets direct blocks from stratum and communicates with backup node as well as with other nodes on the internet to get this block propagated as fast as possible on the network.

"Bad" or "malicious" peers are or at least SHOULD be automatically banned by the daemon, you can see that as "misbehaving" in the log of the daemon.
If that doesn't work or is disabled intentionally you or ALL peers are having a BIG problems, as EVERYONE with an open wallet is vulnerable to those attacks.

Oh and btw, you firewall expert, you of course CAN block incoming connections and only allow outgoing connections but what about the incoming data over the outgoing connection ? So you don't want to accept any traffic coming in ?

By making your node public it starts to become probed for collateral, relays encrypted data, votes, seeds the blockchain, etc for services such as ZeroTime, Node Incentives and Chainblender. Because other nodes can connect to you will seed the blockchain to other peers more often and possibly see increased memory growth from Berkeley DB keeping excessive dirty pages. By firewalling your node it will keep a fairly constant memory pattern as it is only performing relaying. The only reason to have the p2p port public is if you intend something described here.

And this is exactly what is needed

Btw in bitcoin/dash nodes you can limit all those stuff in the config file.. "rpcmaxconnections" etc..

If you disable incoming connections or disallow incoming traffic at all, your node will have only 1 connection (the outgoing connection) and you'll have lots of orphans and lots of problems when that one connection goes down.

Still XVC has a big problem with authentication. By default it listens on  port 9995 without any username or password or even host authentication which of course makes it a viable target for hackers. At least it defaults to 127.0.0.1 but IMHO it shouldn't be possible at all to allow listening on any port without password (rpcusername) or hostname (rpcallowip) auth. But yes, this can be fixed by iptables etc... Hopefully everyone does that...

[kalisto]

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

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

Hey your Bitcointalk account is exposed to the public. Your account is vulnerable. I will ask the mods to ban your account.

This is how stupid John his theory sounded when he said suprnova is not safe.

To mine, a pool need to have open ports.. Otherwise you can't connect.

He had nothing to back up with except bluffing /lying.
But maybe you are a pro network engineer and be able show everyone a detailed security analysis.

If you dont close your inbound tcp ports for the daemon you are not qualified to run a pool lol.

Stratum is the only port that should be open to the public and talks internal to the daemon.

Crybabies

Lol and the daemon talks to itself because it isn't allowed to communicate with other peers, right?

You have p2p ports and rpc ports.  Of course close the rpc port but p2p is the port which connects to other daemons, other wallets...

Drunk?

LOL i get it, you dont know how a firewall works.
You dont want external peers connecting to your node, you submit your work to the network.
Only outbound is important so you get a firewalled peer, how else does the BTC client work behind a router with closed ports? ROFLOL

Are you really that stupid? 

LOL, I see a real network expert here




Of course you want external nodes connecting to your node, this will propagate your blocks faster, especialy when you're a pool. You always want as much connections as possible, your're not a peer, you're a pool.. If you're not connecting well, your Blocks won't propagate fast and you'll have problems with orphans. Thats also the reason why there's always a main and a backup node, one gets direct blocks from stratum and communicates with backup node as well as with other nodes on the internet to get this block propagated as fast as possible on the network.

"Bad" or "malicious" peers are or at least SHOULD be automatically banned by the daemon, you can see that as "misbehaving" in the log of the daemon.
If that doesn't work or is disabled intentionally you or ALL peers are having a BIG problems, as EVERYONE with an open wallet is vulnerable to those attacks.

Oh and btw, you firewall expert, you of course CAN block incoming connections and only allow outgoing connections but what about the incoming data over the outgoing connection ? So you don't want to accept any traffic coming in ?

By making your node public it starts to become probed for collateral, relays encrypted data, votes, seeds the blockchain, etc for services such as ZeroTime, Node Incentives and Chainblender. Because other nodes can connect to you will seed the blockchain to other peers more often and possibly see increased memory growth from Berkeley DB keeping excessive dirty pages. By firewalling your node it will keep a fairly constant memory pattern as it is only performing relaying. The only reason to have the p2p port public is if you intend something described here.

And this is exactly what is needed

Btw in bitcoin/dash nodes you can limit all those stuff in the config file.. "rpcmaxconnections" etc..

If you disable incoming connections or disallow incoming traffic at all, your node will have only 1 connection (the outgoing connection) and you'll have lots of orphans and lots of problems when that one connection goes down.

Still XVC has a big problem with authentication. By default it listens on  port 9995 without any username or password or even host authentication which of course makes it a viable target for hackers. At least it defaults to 127.0.0.1 but IMHO it shouldn't be possible at all to allow listening on any port without password (rpcusername) or hostname (rpcallowip) auth. But yes, this can be fixed by iptables etc... Hopefully everyone does that...

No it's not needed, as long as you have 8 outbound connections there are no problems.
Inbound = overhead, rest should get handled with proper opsec.
I'm just explaining why your pool forked on xvc, its not your so called paranoid backdoor.

[mrsky]

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.

[ocminer]

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

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

Hey your Bitcointalk account is exposed to the public. Your account is vulnerable. I will ask the mods to ban your account.

This is how stupid John his theory sounded when he said suprnova is not safe.

To mine, a pool need to have open ports.. Otherwise you can't connect.

He had nothing to back up with except bluffing /lying.
But maybe you are a pro network engineer and be able show everyone a detailed security analysis.

If you dont close your inbound tcp ports for the daemon you are not qualified to run a pool lol.

Stratum is the only port that should be open to the public and talks internal to the daemon.

Crybabies

Lol and the daemon talks to itself because it isn't allowed to communicate with other peers, right?

You have p2p ports and rpc ports.  Of course close the rpc port but p2p is the port which connects to other daemons, other wallets...

Drunk?

LOL i get it, you dont know how a firewall works.
You dont want external peers connecting to your node, you submit your work to the network.
Only outbound is important so you get a firewalled peer, how else does the BTC client work behind a router with closed ports? ROFLOL

Are you really that stupid? 

LOL, I see a real network expert here




Of course you want external nodes connecting to your node, this will propagate your blocks faster, especialy when you're a pool. You always want as much connections as possible, your're not a peer, you're a pool.. If you're not connecting well, your Blocks won't propagate fast and you'll have problems with orphans. Thats also the reason why there's always a main and a backup node, one gets direct blocks from stratum and communicates with backup node as well as with other nodes on the internet to get this block propagated as fast as possible on the network.

"Bad" or "malicious" peers are or at least SHOULD be automatically banned by the daemon, you can see that as "misbehaving" in the log of the daemon.
If that doesn't work or is disabled intentionally you or ALL peers are having a BIG problems, as EVERYONE with an open wallet is vulnerable to those attacks.

Oh and btw, you firewall expert, you of course CAN block incoming connections and only allow outgoing connections but what about the incoming data over the outgoing connection ? So you don't want to accept any traffic coming in ?

By making your node public it starts to become probed for collateral, relays encrypted data, votes, seeds the blockchain, etc for services such as ZeroTime, Node Incentives and Chainblender. Because other nodes can connect to you will seed the blockchain to other peers more often and possibly see increased memory growth from Berkeley DB keeping excessive dirty pages. By firewalling your node it will keep a fairly constant memory pattern as it is only performing relaying. The only reason to have the p2p port public is if you intend something described here.

And this is exactly what is needed

Btw in bitcoin/dash nodes you can limit all those stuff in the config file.. "rpcmaxconnections" etc..

If you disable incoming connections or disallow incoming traffic at all, your node will have only 1 connection (the outgoing connection) and you'll have lots of orphans and lots of problems when that one connection goes down.

Still XVC has a big problem with authentication. By default it listens on  port 9995 without any username or password or even host authentication which of course makes it a viable target for hackers. At least it defaults to 127.0.0.1 but IMHO it shouldn't be possible at all to allow listening on any port without password (rpcusername) or hostname (rpcallowip) auth. But yes, this can be fixed by iptables etc... Hopefully everyone does that...

No it's not needed, as long as you have 8 outbound connections there are no problems.
Inbound = overhead, rest should get handled with proper opsec.
I'm just explaining why your pool forked on xvc, its not your so called paranoid backdoor.

I disagree, the pool running like this for years until JC in public stated he banned my pools node(s). (Check twitter pics!) It forked because he used his code and banned the pools IP and/or wallet address, not because anything on pools side was improperly configured or not going normal. He was actively fighting against the pool as said so in his twitter.

[DeadBirdzz]

hmmmmm, who should I trust?

OCMINER or that fucking dramaqueen called "John Connor" who just ass fucked a lot of his investors without any lube?

Decisions, Decisions.....

[thelion07]

John Lennon - Adam and Eve 

[hughbt]

Badass said on xvc slack that he "is sure that John will come back to take over this under different pseudonym". And now all of a sudden Badass tries to lead a takeover. Is this John trying to shift attention to someone else? He already did this once saying that "MM" is controlling the market but this mythical MM was John himself.
Now I'm not sure if Mazz was just a sockpuppet or he is a part of this con and he is playing a victim.

First of all new XVC devs should not be anonymous.

[BadAss.Sx]

Badass said on xvc slack that he "is sure that John will come back to take over this under different pseudonym". And now all of a sudden Badass tries to lead a takeover. Is this John trying to shift attention to someone else? He already did this once saying that "MM" is controlling the market but this mythical MM was John himself.
Now I'm not sure if Mazz was just a sockpuppet or he is a part of this con and he is playing a victim.

First of all new XVC devs should not be anonymous.

Yes, i'm JC 

[indri123]

It's too early to say john-connor abandoned XVC. You guys should wait until the beginning of next year.

[BadAss.Sx]

yeah sure, everyone lost a bunch of BTC's and we should wait for a positive reaction from him until next year. If it wasn't him, why is he not coming to Slack then?

[indri123]

yeah sure, everyone lost a bunch of BTC's and we should wait for a positive reaction from him until next year. If it wasn't him, why is he not coming to Slack then?

1) He got banned from slack.
2) You have your takeover https://github.com/vcashcommunity/

[Fidel007]

yeah sure, everyone lost a bunch of BTC's and we should wait for a positive reaction from him until next year. If it wasn't him, why is he not coming to Slack then?

1) He got banned from slack.
2) You have your takeover https://github.com/vcashcommunity/

Time to get the popcorn

 

[placebo]

I will not say anything else tomorrow XVC is my coin too and i collected the BTCs. I'm waiting for the first messages

[MaryAngela_Fantocci]

I have the basic HTML skills and I can build the Excel's diagrams.
That's enough to become the new developer?

[EmilioMann]

yeah sure, everyone lost a bunch of BTC's and we should wait for a positive reaction from him until next year. If it wasn't him, why is he not coming to Slack then?

1) He got banned from slack.
2) You have your takeover https://github.com/vcashcommunity/

Dont trust that.
Many people, including me, have cloned the code before all this shit.
John Connor did modifications yesterday shortly before that fork was created, probably filled with exploits.

[NakeSLam11]

I am interested in development of this coin.

[gawlea]

I'l be watcking this coin, sound interesting.

[EmilioMann]

If mazz isnt part of the JC's scam, why does he continue deleting posts on the community's official thread?

https://bitcointalk.org/index.php?topic=1578775.140

[Lemaxho]

Looks like JC identity has been found

https://bitcointalk.org/index.php?topic=1504342.msg17074316#msg17074316

[Jumanji7]

Let`s make XVC great again!