3x HD5870 = 1300Mhash/s Never rebooted it in 8 days now Rock solid @ 3x 437Mhash/s. 2x Gigabyte HD7970 And this one is rock solid too
|
|
|
So when miners run away, it won't go lower and you'll be mining at a big loss and/or coin dies?
|
|
|
Yep, my client is about 24 hours old, therefore not the latest. Probably is the reason for my issue so going to pull from git and recompile. Thanks!
Terracoin changes clients more often as I change my socks. And I change my socks every day...
|
|
|
If you really want to be cautious, backup your wallet. If you are on the forked chain, you will not lose your coins,
Unless you mined them or mined on a pool using an orphaned chain... That happened to 30% of my coins, the other coins matured. That's one of the reasons I stop mining TRC until it is solved. I don't like to waste my GPU cycles on an orphaned chain...
|
|
|
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.
Exactly the reason i wrote what I did. You have probably been on various nodes banned list from time to time throughout your use of crypto-coins and not even noticed. Anyway, it is fine. In fact I will go back and strike out my statement, and everybody publish all the node banned lists you want. It might be slightly entertaining to watch all the panic that might ensue.... Oh, and BTC-E is on the right fork, I have been able to move TRC in since this mourning (I updated all my systems when I updated Cryptocoinexplorer last night). So if your up to date and you block height matches the explorer..go for it. If you really want to be cautious, backup your wallet. If you are on the forked chain, you will not lose your coins, However it can be a pain in the but to remove the transaction from your wallet so your client does not see the coins as spent. (You can us PYwallet to erase the transactions from a wallet if that happens) I can confirm BTC-E is on the right chain (or at least on my chain)
|
|
|
To test things I did two things now: I sent 0.5 TRC to BTC-E on the old address that I use for a while now. Then I generated a new address in BTC-E and sent another 0.5 TRC. All for the sake of science Now wait if they show up @ BTC-E... If they don't it's borked?
|
|
|
Mining in P2Pool I got on the "banned nodes list" while using the most recent client, mining on the right chain and 2700Mhash/s. Looks like there are at least 2 chains, when I look in the P2Pool statistics:
|
|
|
I already have this version for 10 hours or so. When I woke up, I updated my wallet to -33 and installed/configured Python, Twister and P2Pool because multipool.in was offline, again... While mining P2Pool, approx. 30% of my mined coins disappeared (rejected), others (before and after) matured without problems.
|
|
|
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 LISTSAs 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.
|
|
|
DO NOT WORRY IF YOU ARE ON A NODES BANNED LIST...AND PLEASE STOP PUBLISHING NODE BANNED LISTS
Unless you are having problems connecting to the network, and are being blocked by multiple nodes, it is nothing to worry about.
Just make sure you are using the latest client. TRC is having enough issues without starting another completely unnecessary fire.
To avoid such confusions the devs might want to publish chain forking changes a little bit earlier (less than a day, seriously?) and/or broadcast a message like Bitcoin devs did when their chain forked. Apparently they are even quite a lot of miners on a previous fork (so that makes it at least 3 simultaneous TRC chains) on P2Pool as MaGNet's previous post shows. Both my clients are @ block 104.380 as we speak. I am able to move coins around, just tested it with 0.5 TRC
|
|
|
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 means a lot since Terracoin is legit hard-forked on block 104290. Banscore 100 is absolutely rare in normal occassions. For example, double spend attempt (sending tx which constains already spent outputs) will earn you banscore of just 10. @ MaGNeT Reset your IP than start wallet again. When in miner, check what difficulty it shows, write it down, wait the next block then compare difficulty you wrote down with one shown on Terracoin explorer. If they are same, you are fine. Reset my IP? How do you mean? I have this IP for 4 years now and can't be changed.
|
|
|
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? Just did a git pull, saw one commit, git diff HEAD^ shows ugly hacks testing a minimum block that was already reached. The commit was published less than 24h before it was needed to remain on the main chain, that's quite brutal. I wonder if all exchanges are on the right chain and how they will react if they aren't... These are my statistics from P2Pool. Why are there 104.xxx and 100.xxx blocks? Or isn't that the blockchain?
|
|
|
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.
|
|
|
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?
|
|
|
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?
|
|
|
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.
|
|
|
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 = eclipsemc3373 3373 // 176.9.104 = bitminter3374 3374 // 62.113.214 192.198.93 59.167.117 = ozcoin 3375 + // 72.135.241.30 = big fake blocks from here3375 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/24f6dd64bb64bc930d114335185f317d79a63c96Other 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:
|
|
|
It was fun to find out how to get P2Pool running anyway
|
|
|
There are close to 15m bqc, valued at 1k/btc would give a market cap of 15,000 btc, which is higher than every coin below namecoin, put it another way, 15k btc is about the market cap of devcoin, novacoin, terracoin and freicoin combined.
Well it's your money so if you want to throw it away nobody can stop you.
Nonsense. Value of LTC is now 0.02xxx BTC, value of NMC is now 0.04xxx BTC, Nothing wrong with a 0.001xxx value for BQC, it's actually very low for an (currently) ASIC proof Scryptcoin.
|
|
|
It's all about not believing something good is going to happen to you when you buy them, it's not about trust in LTC, it's about trust in yourself and your judgement.
I heared the same doubts in 2010/2011, in the time someone bought a pizza for 10,000 BTC. Yes... A one million Dollar pizza...
Captain Hindsight will visit you if you don't have some LTC stacked up now.
|
|
|
|