Actually, the non-x card is the next 6-9 that I will be purchasing. I'm just trying to go Amazon to be able to use BTC via Gyft. If I don't pull the trigger on those today, I'll be piece-mealing a bunch of 270Xs.
Didn't post this on the main thread for obvious reasons.
John,
I agree wholeheartedly... with an orphan rate of nearly 33%... just check the 24hr stats - 61 blocks found - 43 valid - 18 orphans... TAG is no longer a profitable coin to mine for me... and as everyone here knows I am a big TAG fan and been mining since the beginning as well... Mark and the team must address this... it is vital for the long-term usefulness of the coin... and if Mark does not know how to remedy this problem... then the coin faces a real long-term confidence issue.
Fuse is in no way implicated in this fiasco... he has set a gold standard for pool admins... and he has to be extremely frustrated to see this happening after all the hard work, energy and real money he has invested in this pool.
I have moved on... I am mining EarthCoin... the other coin that I believe has real potential and usefulness... now and in the future... and it is reasonably profitable to mine... at least until it starts getting hit with multi-pools.
Fuse... you know I will support any pools that you choose to open to counter your losses from TAG.
EDIT - Another orphan - #28256 - that makes two in a row.
I am with you guys 100%. In fact if you look back in the main thread, I was one of the first people, if not the first person, to bring up the unusually high orphan rates. I understand that people are saying that it is correcting itself, but lets say TAG gets as big as LTC. Take one of the top pools, GiveMeCoins, and they are hashing at about 8-9GH. That's 8-9 times what Botpool is doing. If we're seeing issues with one pool at 1GH and the rest equaling about 1GH, what is going to happen when the network hits 10GH?
I agree with your concerns and complaints. It's very difficult for me to look at the block page and see it dotted with ORPHAN ORPHAN ORPHAN ORPHAN. It's especially hard when you can't do anything about it because it's not a server issue.
I think if anything is to be done about it, the difficulty needs to retarget every X amount of blocks. I say 10-20 blocks. That's every few hours if things are running smooth. I think it would help to even out the difficulty, and reduce the issues we're seeing. I really do think the wild swings are what are causing a majority of the issues... as well as Botpool being such a blubbering whale in Asia. But I'm working on that .
In the meantime, I think we should campaign for the difficulty to retarget less often. Even if that doesn't solve the orphan issue, it will smooth out the round targets, and stabilize the rewards a little bit.
-Fuse