Spam Terracoin?

[wmikrut]

I agree with dreamwatcher that it's rather premature and weak to quit at this moment.

By all means terracoin hasn't even tried ppc's adjustment yet. ppcoin itself should be pretty safe from this because of proof-of-stake protection. As for a pure proof-of-work implementation, I think even with some ASIC miner exploiting it, at worst it could probably extend the block spacing from 2 minute to maybe 20 minutes sometimes. Given a reasonably long averaging window it shouldn't be all that intolerable.

The problem is DEV for terracoin is so taciturn...

the comments are all gone from git hub, but all the code remains last time I checked...

something is realllly of here....

I note that Crazy Rabbit mentioned having and Asic at some...stage...and that he could consider using it on the TRC chain (in support of the chain I inferred).

Crazy Rabbit can you clear this up??

I do not have an ASIC. I had a preorder for a BFL, but (smartest move I ever made) I never paid for it. I have 3x 6950's. They are mining litecoin now.

hmm do you recall crypto chat the other day or was that someone hoaxing as you....your account may be compromised?

that was me chatting to you. However if my account was compromised, thats what I would tell you anyway. My passwords are very long and secure.

To be honest I think the rabbit hole goes no deeper then some kid with an ASIC decided to f*ck up our hard work.

I agree... all the 'compromised' blocks all appeared to be coming from a single ip address. 
imo this essentially points to a single location responsible for the attack.

[jubalix]

I think TRC is the pet chain of someone with asics....may be in league with some one at an exchange or exchanges a  clever scheme to suck BTC//$$$ out and some tame devs or devs in league

The DEV's actions cannot be explained, and they were clever....I mean they had the email addresses of the DEV sunnyking confirmed that was the email address no spoof has been checked....

BTCe just shuts up after its inital foray....(maybe they will comment agian)

Repo's moved around comments deleted

FUD sell

and BTCe says nothing.....

Hard to transfer funds from Vircure to BTC e

no....there is definitely some planing and collusion here, some one that could get and asic and run it would not be wasting it

Dev can code but screws around with solutions that just don't quite work, fuds, repos moved, then releases next patch, SunnyKing told him to look at how he does it....No comment...would not use that ?

What we should do is this Get the re-target code from sunnyking put it in the Terracoin code and release that....!!!!

That would probably upset the applecart and bring a few worms out of the can....I would be interested to see if TRC was desisted at that point when it was working....

I agree with dreamwatcher that it's rather premature and weak to quit at this moment.

By all means terracoin hasn't even tried ppc's adjustment yet. ppcoin itself should be pretty safe from this because of proof-of-stake protection. As for a pure proof-of-work implementation, I think even with some ASIC miner exploiting it, at worst it could probably extend the block spacing from 2 minute to maybe 20 minutes sometimes. Given a reasonably long averaging window it shouldn't be all that intolerable.

The problem is DEV for terracoin is so taciturn...

the comments are all gone from git hub, but all the code remains last time I checked...

something is realllly of here....

I note that Crazy Rabbit mentioned having and Asic at some...stage...and that he could consider using it on the TRC chain (in support of the chain I inferred).

Crazy Rabbit can you clear this up??

I do not have an ASIC. I had a preorder for a BFL, but (smartest move I ever made) I never paid for it. I have 3x 6950's. They are mining litecoin now.

hmm do you recall crypto chat the other day or was that someone hoaxing as you....your account may be compromised?

that was me chatting to you. However if my account was compromised, thats what I would tell you anyway. My passwords are very long and secure.

To be honest I think the rabbit hole goes no deeper then some kid with an ASIC decided to f*ck up our hard work.

[SRoulette]

I think TRC is the pet chain of someone with asics....may be in league with some one at an exchange or exchanges a  clever scheme to suck BTC//$$$ out and some tame devs or devs in league

The DEV's actions cannot be explained, and they were clever....I mean they had the email addresses of the DEV sunnyking confirmed that was the email address no spoof has been checked....

BTCe just shuts up after its inital foray....(maybe they will comment agian)

Repo's moved around comments deleted

FUD sell

and BTCe says nothing.....

Hard to transfer funds from Vircure to BTC e

no....there is definitely some planing and collusion here, some one that could get and asic and run it would not be wasting it

Dev can code but screws around with solutions that just don't quite work, fuds, repos moved, then releases next patch, SunnyKing told him to look at how he does it....No comment...would not use that ?

What we should do is this Get the re-target code from sunnyking put it in the Terracoin code and release that....!!!!

That would probably upset the applecart and bring a few worms out of the can....I would be interested to see if TRC was desisted at that point when it was working....

I agree with dreamwatcher that it's rather premature and weak to quit at this moment.

By all means terracoin hasn't even tried ppc's adjustment yet. ppcoin itself should be pretty safe from this because of proof-of-stake protection. As for a pure proof-of-work implementation, I think even with some ASIC miner exploiting it, at worst it could probably extend the block spacing from 2 minute to maybe 20 minutes sometimes. Given a reasonably long averaging window it shouldn't be all that intolerable.

The problem is DEV for terracoin is so taciturn...

the comments are all gone from git hub, but all the code remains last time I checked...

something is realllly of here....

I note that Crazy Rabbit mentioned having and Asic at some...stage...and that he could consider using it on the TRC chain (in support of the chain I inferred).

Crazy Rabbit can you clear this up??

I do not have an ASIC. I had a preorder for a BFL, but (smartest move I ever made) I never paid for it. I have 3x 6950's. They are mining litecoin now.

hmm do you recall crypto chat the other day or was that someone hoaxing as you....your account may be compromised?

that was me chatting to you. However if my account was compromised, thats what I would tell you anyway. My passwords are very long and secure.

To be honest I think the rabbit hole goes no deeper then some kid with an ASIC decided to f*ck up our hard work.

I support a fork to save terracoin if thats what it takes.

[jubalix]

I think TRC is the pet chain of someone with asics....may be in league with some one at an exchange or exchanges a  clever scheme to suck BTC//$$$ out and some tame devs or devs in league

The DEV's actions cannot be explained, and they were clever....I mean they had the email addresses of the DEV sunnyking confirmed that was the email address no spoof has been checked....

BTCe just shuts up after its inital foray....(maybe they will comment agian)

Repo's moved around comments deleted

FUD sell

and BTCe says nothing.....

Hard to transfer funds from Vircure to BTC e

no....there is definitely some planing and collusion here, some one that could get and asic and run it would not be wasting it

Dev can code but screws around with solutions that just don't quite work, fuds, repos moved, then releases next patch, SunnyKing told him to look at how he does it....No comment...would not use that ?

What we should do is this Get the re-target code from sunnyking put it in the Terracoin code and release that....!!!!

That would probably upset the applecart and bring a few worms out of the can....I would be interested to see if TRC was desisted at that point when it was working....

I agree with dreamwatcher that it's rather premature and weak to quit at this moment.

By all means terracoin hasn't even tried ppc's adjustment yet. ppcoin itself should be pretty safe from this because of proof-of-stake protection. As for a pure proof-of-work implementation, I think even with some ASIC miner exploiting it, at worst it could probably extend the block spacing from 2 minute to maybe 20 minutes sometimes. Given a reasonably long averaging window it shouldn't be all that intolerable.

The problem is DEV for terracoin is so taciturn...

the comments are all gone from git hub, but all the code remains last time I checked...

something is realllly of here....

I note that Crazy Rabbit mentioned having and Asic at some...stage...and that he could consider using it on the TRC chain (in support of the chain I inferred).

Crazy Rabbit can you clear this up??

I do not have an ASIC. I had a preorder for a BFL, but (smartest move I ever made) I never paid for it. I have 3x 6950's. They are mining litecoin now.

hmm do you recall crypto chat the other day or was that someone hoaxing as you....your account may be compromised?

that was me chatting to you. However if my account was compromised, thats what I would tell you anyway. My passwords are very long and secure.

To be honest I think the rabbit hole goes no deeper then some kid with an ASIC decided to f*ck up our hard work.

I support a fork to save terracoin if thats what it takes.

Get Sunnyking to use his target system into TRC and fork, TradeFortress could do it as well

[celkaris]

This is one person with one ASIC.

As much I understand the code, it is so much worse than one person with one ASIC:
[...]
https://github.com/terracoin/terracoin/commit/24f6dd64bb64bc930d114335185f317d79a63c96

nice commit message xD :

[core] logging: log remote ip address while receiving a block.

- can't do much, if you are able to mine every single block at 5 to 10
   times the usual net diff ... you won

[wmikrut]

This is one person with one ASIC.

As much I understand the code, it is so much worse than one person with one ASIC:

3372    3372             // 69.195.155 96.43.135 208.110.68 = eclipsemc
3373    3373             // 176.9.104 = bitminter
3374    3374             // 62.113.214 192.198.93 59.167.117 = ozcoin
     3375    +        // 72.135.241.30 = big fake blocks from here
3375    3376             if (boost::algorithm::starts_with(pfrom->addr.ToString(), "23.21.225")
3376    3377                     || boost::algorithm::starts_with(pfrom->addr.ToString(), "176.31.157")
3377    3378                     || boost::algorithm::starts_with(pfrom->addr.ToString(), "46.4.121")
...    ...    @@ -3382,7 +3383,8 @@ bool static ProcessMessage(CNode* pfrom, string strCommand, CDataStream& vRecv)
3382    3383                     || boost::algorithm::starts_with(pfrom->addr.ToString(), "176.9.104")
3383    3384                     || boost::algorithm::starts_with(pfrom->addr.ToString(), "62.113.214")
3384    3385                     || boost::algorithm::starts_with(pfrom->addr.ToString(), "192.198.93")
3385         -                || boost::algorithm::starts_with(pfrom->addr.ToString(), "59.167.117"))
     3386    +                || boost::algorithm::starts_with(pfrom->addr.ToString(), "59.167.117")
     3387    +                || boost::algorithm::starts_with(pfrom->addr.ToString(), "72.135.241"))
3386    3388             {
3387    3389                 pfrom->Misbehaving(100);
3388    3390                 //printf("Banned remote node from addr=%s ; known terracoin pool.\n", pfrom->addr.ToString().c_str());
...    ...    @@ -3883,7 +3885,7 @@ bool static ProcessMessage(CNode* pfrom, string strCommand, CDataStream& vRecv)
3883    3885             CBlock block;
3884    3886             vRecv >> block;

https://github.com/terracoin/terracoin/commit/24f6dd64bb64bc930d114335185f317d79a63c96

This just shows there was an attempt to ban all traffic from 72.13.241 range.
The person was probably using multiple ips within that segment.

Note:  I ignored 3372-3374... because 3375 was just added.
There could be a valid reason to ignore other pools.. perhaps this attack started elsewhere and progressed.

[MaGNeT]

It was fun to find out how to get P2Pool running anyway

[SRoulette]

This is one person with one ASIC.

As much I understand the code, it is so much worse than one person with one ASIC:

3372    3372             // 69.195.155 96.43.135 208.110.68 = eclipsemc
3373    3373             // 176.9.104 = bitminter
3374    3374             // 62.113.214 192.198.93 59.167.117 = ozcoin
     3375    +        // 72.135.241.30 = big fake blocks from here
3375    3376             if (boost::algorithm::starts_with(pfrom->addr.ToString(), "23.21.225")
3376    3377                     || boost::algorithm::starts_with(pfrom->addr.ToString(), "176.31.157")
3377    3378                     || boost::algorithm::starts_with(pfrom->addr.ToString(), "46.4.121")
...    ...    @@ -3382,7 +3383,8 @@ bool static ProcessMessage(CNode* pfrom, string strCommand, CDataStream& vRecv)
3382    3383                     || boost::algorithm::starts_with(pfrom->addr.ToString(), "176.9.104")
3383    3384                     || boost::algorithm::starts_with(pfrom->addr.ToString(), "62.113.214")
3384    3385                     || boost::algorithm::starts_with(pfrom->addr.ToString(), "192.198.93")
3385         -                || boost::algorithm::starts_with(pfrom->addr.ToString(), "59.167.117"))
     3386    +                || boost::algorithm::starts_with(pfrom->addr.ToString(), "59.167.117")
     3387    +                || boost::algorithm::starts_with(pfrom->addr.ToString(), "72.135.241"))
3386    3388             {
3387    3389                 pfrom->Misbehaving(100);
3388    3390                 //printf("Banned remote node from addr=%s ; known terracoin pool.\n", pfrom->addr.ToString().c_str());
...    ...    @@ -3883,7 +3885,7 @@ bool static ProcessMessage(CNode* pfrom, string strCommand, CDataStream& vRecv)
3883    3885             CBlock block;
3884    3886             vRecv >> block;

https://github.com/terracoin/terracoin/commit/24f6dd64bb64bc930d114335185f317d79a63c96

This just shows there was an attempt to ban all traffic from 72.13.241 range.
The person was probably using multiple ips within that segment.

It would be cool to know if miners mining in those pools have any idea about the pool operator deeds.

Thanks, thats a nice list of unfriendly altcoin pools to avoid

[dreamwatcher]

This is one person with one ASIC.

As much I understand the code, it is so much worse than one person with one ASIC:

3372    3372             // 69.195.155 96.43.135 208.110.68 = eclipsemc
3373    3373             // 176.9.104 = bitminter
3374    3374             // 62.113.214 192.198.93 59.167.117 = ozcoin
     3375    +        // 72.135.241.30 = big fake blocks from here
3375    3376             if (boost::algorithm::starts_with(pfrom->addr.ToString(), "23.21.225")
3376    3377                     || boost::algorithm::starts_with(pfrom->addr.ToString(), "176.31.157")
3377    3378                     || boost::algorithm::starts_with(pfrom->addr.ToString(), "46.4.121")
...    ...    @@ -3382,7 +3383,8 @@ bool static ProcessMessage(CNode* pfrom, string strCommand, CDataStream& vRecv)
3382    3383                     || boost::algorithm::starts_with(pfrom->addr.ToString(), "176.9.104")
3383    3384                     || boost::algorithm::starts_with(pfrom->addr.ToString(), "62.113.214")
3384    3385                     || boost::algorithm::starts_with(pfrom->addr.ToString(), "192.198.93")
3385         -                || boost::algorithm::starts_with(pfrom->addr.ToString(), "59.167.117"))
     3386    +                || boost::algorithm::starts_with(pfrom->addr.ToString(), "59.167.117")
     3387    +                || boost::algorithm::starts_with(pfrom->addr.ToString(), "72.135.241"))
3386    3388             {
3387    3389                 pfrom->Misbehaving(100);
3388    3390                 //printf("Banned remote node from addr=%s ; known terracoin pool.\n", pfrom->addr.ToString().c_str());
...    ...    @@ -3883,7 +3885,7 @@ bool static ProcessMessage(CNode* pfrom, string strCommand, CDataStream& vRecv)
3883    3885             CBlock block;
3884    3886             vRecv >> block;

https://github.com/terracoin/terracoin/commit/24f6dd64bb64bc930d114335185f317d79a63c96

This just shows there was an attempt to ban all traffic from 72.13.241 range.
The person was probably using multiple ips within that segment.

It would be cool to know if miners mining in those pools have any idea about the pool operator deeds.

Thanks, thats a nice list of unfriendly altcoin pools to avoid

I am not too sure about this.

eclipsemc = I could maybe see Josh doing this since he does work for BFL.

Bitminter = I dont know the owner enough to comment

  Ozcoin = I highly doubt Graet would have anything to do with manipulation/attacking a coin chain. It just seems way too out of character  for him, like miles and miles out of character.   

Have the Terracoin Developers contacted the owners of these pools to see what is going on? Something just does not seem right, especially coming from Ozcoin.

[celkaris]

I am not too sure about this.

hrm .. me neither, reading this forum, i'd expect to see another famous one, but not necessarily those. Are there any others in this list ? are all known popular pools in that list ?

[MaGNeT]

This is one person with one ASIC.

As much I understand the code, it is so much worse than one person with one ASIC:

3372    3372             // 69.195.155 96.43.135 208.110.68 = eclipsemc
3373    3373             // 176.9.104 = bitminter
3374    3374             // 62.113.214 192.198.93 59.167.117 = ozcoin
     3375    +        // 72.135.241.30 = big fake blocks from here
3375    3376             if (boost::algorithm::starts_with(pfrom->addr.ToString(), "23.21.225")
3376    3377                     || boost::algorithm::starts_with(pfrom->addr.ToString(), "176.31.157")
3377    3378                     || boost::algorithm::starts_with(pfrom->addr.ToString(), "46.4.121")
...    ...    @@ -3382,7 +3383,8 @@ bool static ProcessMessage(CNode* pfrom, string strCommand, CDataStream& vRecv)
3382    3383                     || boost::algorithm::starts_with(pfrom->addr.ToString(), "176.9.104")
3383    3384                     || boost::algorithm::starts_with(pfrom->addr.ToString(), "62.113.214")
3384    3385                     || boost::algorithm::starts_with(pfrom->addr.ToString(), "192.198.93")
3385         -                || boost::algorithm::starts_with(pfrom->addr.ToString(), "59.167.117"))
     3386    +                || boost::algorithm::starts_with(pfrom->addr.ToString(), "59.167.117")
     3387    +                || boost::algorithm::starts_with(pfrom->addr.ToString(), "72.135.241"))
3386    3388             {
3387    3389                 pfrom->Misbehaving(100);
3388    3390                 //printf("Banned remote node from addr=%s ; known terracoin pool.\n", pfrom->addr.ToString().c_str());
...    ...    @@ -3883,7 +3885,7 @@ bool static ProcessMessage(CNode* pfrom, string strCommand, CDataStream& vRecv)
3883    3885             CBlock block;
3884    3886             vRecv >> block;

https://github.com/terracoin/terracoin/commit/24f6dd64bb64bc930d114335185f317d79a63c96

Other missbehaving peers that earned themselves banscore 100 since block 104290:

*** LIST OF IP'S ***

I can assure you my IP is on that list and I'm only mining with 3x HD5870 and 2x HD7970 GPU cards @ P2Pool (2700Mhash/s) for 7 hours now.
Before that I was on multipool.in but that pool isn't stable.
Why am I banned?

edit: fired up my rig again:

[celkaris]

old client maybe ? i just updated mine and everything looks good til now.

[MaGNeT]

Your current Terracoin wallet is submitting or relaying invalid blocks, for example:

2013-04-13 16:24:14 received block 0000000000245a6c0f603705df6ff3b3aa8149d2319def5ed0e4023e86bd1b48 from 46.73.147.179:62383
2013-04-13 16:24:14 ERROR: AcceptBlock() : incorrect proof of work
2013-04-13 16:24:14 ERROR: ProcessBlock() : AcceptBlock FAILED
2013-04-13 16:24:14 Misbehaving: 46.73.147.179:62383 (0 -> 100) DISCONNECTING
2013-04-13 16:24:14 disconnecting node 46.73.147.179:62383

Upgrade to newest version as soon as possible!

What is the newest version?
I have the terracoin-0.1.3-33-win32 running on my mining rig.

[dreamwatcher]

This is one person with one ASIC.

As much I understand the code, it is so much worse than one person with one ASIC:

3372    3372             // 69.195.155 96.43.135 208.110.68 = eclipsemc
3373    3373             // 176.9.104 = bitminter
3374    3374             // 62.113.214 192.198.93 59.167.117 = ozcoin
     3375    +        // 72.135.241.30 = big fake blocks from here
3375    3376             if (boost::algorithm::starts_with(pfrom->addr.ToString(), "23.21.225")
3376    3377                     || boost::algorithm::starts_with(pfrom->addr.ToString(), "176.31.157")
3377    3378                     || boost::algorithm::starts_with(pfrom->addr.ToString(), "46.4.121")
...    ...    @@ -3382,7 +3383,8 @@ bool static ProcessMessage(CNode* pfrom, string strCommand, CDataStream& vRecv)
3382    3383                     || boost::algorithm::starts_with(pfrom->addr.ToString(), "176.9.104")
3383    3384                     || boost::algorithm::starts_with(pfrom->addr.ToString(), "62.113.214")
3384    3385                     || boost::algorithm::starts_with(pfrom->addr.ToString(), "192.198.93")
3385         -                || boost::algorithm::starts_with(pfrom->addr.ToString(), "59.167.117"))
     3386    +                || boost::algorithm::starts_with(pfrom->addr.ToString(), "59.167.117")
     3387    +                || boost::algorithm::starts_with(pfrom->addr.ToString(), "72.135.241"))
3386    3388             {
3387    3389                 pfrom->Misbehaving(100);
3388    3390                 //printf("Banned remote node from addr=%s ; known terracoin pool.\n", pfrom->addr.ToString().c_str());
...    ...    @@ -3883,7 +3885,7 @@ bool static ProcessMessage(CNode* pfrom, string strCommand, CDataStream& vRecv)
3883    3885             CBlock block;
3884    3886             vRecv >> block;

https://github.com/terracoin/terracoin/commit/24f6dd64bb64bc930d114335185f317d79a63c96

Other missbehaving peers that earned themselves banscore 100 since block 104290:

79.135.203.19:13333
70.68.116.189:13333
85.206.129.18:13333
24.93.21.147:13333
188.250.183.163:52752
80.112.166.132:13333
65.29.242.236:65176
70.177.214.76:13333
54.244.216.167:50920
71.12.216.41:64430
122.108.55.177:65220
80.238.171.70:43225
65.129.127.95:13333
180.216.109.196:13333
94.174.43.180:53874
109.171.18.177:62088
186.109.26.90:61613
82.234.193.23:13333
58.7.128.125:51756
188.233.33.191:52870
37.200.37.224:53325
216.67.34.148:52815
2.143.40.177:17907
188.25.252.173:49976
88.168.133.3:52342
89.139.188.28:22521
173.29.240.150:13333
62.163.9.155:13333
124.168.60.187:60870
84.250.96.228:56652
75.145.104.129:23188
173.209.121.239:11481
123.194.192.34:64178
46.73.147.179:62383

I can assure you my IP is on that list and I'm only mining with 3x HD5870 and 2x HD7970 GPU cards @ P2Pool (2700Mhash/s).
Why am I banned?

Ok this answers a few questions.

Just because a node gets "banned" does not mean that the owner of that node is doing anything malicious.

There have been several reports of clients/daemons acting up since this whole thing started, and one node can ban another node for a number of reasons, most of which are not malicious in nature. Something as simple as connecting/disconnecting a bunch of times during communication can get the ban score over the limit. Imagine a user frustrated by recent events opening and closing his client a bunch of times.

Also, IP addresses are not all that reliable. There are a number of ways to spoof them. In fact, it really would not be that hard alter the code in the client/daemon to report whatever it wants. Add to that proxies and TOR, i do not think using IP's through the node network is a reliable way to point fingers. The whole IP system in the client/daemon was really only designed to allow one node to temporary block a node that might be having problems for one reason or the other.Remember node bans are only 24 hours (I believe), this is hardly the design of a system meant to point fingers at malicious operators.

[MaGNeT]

But what consequence does it have now my IP is on that "ban list"?

Can I still mine Terracoin from my home-IP?
Can I still transfer Terracoin from my home-IP?
How do I get off that list?

edit: Back to Litecoin mining. PM me when you fix this.

Edit: my TRC client goes out of sync every now and then, is that a result of the ban?

[dreamwatcher]

But what does it mean now my IP is on that "ban list"?

Can I still mine Terracoin from my home-IP?
Can I still transfer Terracoin from my home-IP?
How do I get off that list?

edit: Back to Litecoin mining. PM me when you fix this.

It means nothing.

It just means that whatever node (client/daemon) that list came from, will not allow your node to connect to it for 24 hours. You will still be able to connect to any other node that has not personally banned your node. The ban only effects the node that issued it.

For whatever reason, that persons node thought your node was misbehaving and this is not uncommon and nothing to worry about unless you find yourself having a hard time getting connected and a bunch of nodes have banned you. This would be an indicator that your client/daemon is malfunctioning in some way.

[MaGNeT]

All IPs listed above were submitting or relaying invalid blocks, which is very bad thing so banscore went from 0 -> 100 immidiately. Listed IPs are of
those who use older wallet versions, so not neccessarily an attacker but I've listed them anyway. From my perspective, there is not so much difference
between ignoring mandatory updates and intentionaly attacking the network.

I used terracoin-0.1.3-33-win32 client during the time I mined at P2Pool because I saw the message it was mandatory from block xxx.xxx.

I didn't know there is a newer one. Where do I find it? On SourceForge this is still the last one.

And "ignoring mandatory updates"? Come on guys... That's about 2-3 "mandatory updates" in 2 days because they f*cked up their own coin?

[gyverlb]

All IPs listed above were submitting or relaying invalid blocks, which is very bad thing so banscore went from 0 -> 100 immidiately. Listed IPs are of
those who use older wallet versions, so not neccessarily an attacker but I've listed them anyway. From my perspective, there is not so much difference
between ignoring mandatory updates and intentionaly attacking the network.

I am in this list. I compiled the client from git master's head less than 24h ago. What nonsense is this? The chain is forked by the devs at a whim?

[MaGNeT]

All IPs listed above were submitting or relaying invalid blocks, which is very bad thing so banscore went from 0 -> 100 immidiately. Listed IPs are of
those who use older wallet versions, so not neccessarily an attacker but I've listed them anyway. From my perspective, there is not so much difference
between ignoring mandatory updates and intentionaly attacking the network.

I am in this list. I compiled the client from git master's head less than 24h ago. What nonsense is this? The chain is forked by the devs at a whim?

Same for me. As soon as I saw the new client and before I started mining at P2Pool, I updated my client to terracoin-0.1.3-33-win32.
I only setup my P2Pool 7-8 hours ago because multipool.in was giving me trouble again and I wanted to mine TRC.

I'm looking around but can't find any newer, so I don't think the problem is at my side.
But I still get banned.

[celkaris]

All IPs listed above were submitting or relaying invalid blocks, which is very bad thing so banscore went from 0 -> 100 immidiately. Listed IPs are of
those who use older wallet versions, so not neccessarily an attacker but I've listed them anyway. From my perspective, there is not so much difference
between ignoring mandatory updates and intentionaly attacking the network.

I am in this list. I compiled the client from git master's head less than 24h ago. What nonsense is this? The chain is forked by the devs at a whim?

Same for me. As soon as I saw the new client and before I started mining at P2Pool, I updated my client to terracoin-0.1.3-33-win32.
I only setup my P2Pool 7-8 hours ago because multipool.in was giving me trouble again and I wanted to mine TRC.

I'm looking around but can't find any newer, so I don't think the problem is at my side.
But I still get banned.

it may work the other way too : you're getting banned by remote nodes still using an older client ?