Quote from: dreamwatcher on April 13, 2013, 05:19:23 PM

Quote from: MaGNeT on April 13, 2013, 05:13:09 PM

Quote from: gyverlb on April 13, 2013, 05:11:49 PM

Quote from: Bitcoin Megastore on April 13, 2013, 05:06:19 PM

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.

DO NOT WORRY IF YOU ARE ON A NODES BANNED LIST...AND PLEASE STOP PUBLISHING NODE BANNED LISTS

As long as I'm on a "nodes banned list" and nobody can explain why, I have all reasons to worry.

I'm trying to mine TRC but it looks broken to me, that's worrying me because I have a shitload of them and I am afraid to send them to BTC-E because I don't know if BTC-E is on the right fork now.