Why is happening? How to fix it? Devs know exact reason?
That's the $64,000 question, mate. There's a few people, including myself, that believe it's some form of attack or network hack. Other's are leaning towards the initial thoughts that it's still a problem with the coin. Either way, no one really knows for sure. Unless Mark(@Tagbond) has a definitive answer on the issue, we're running blind at the moment. -Fuse |
|
|
|
Tell me tagcoin pool where dont have orphaned  ) It's happening everywhere, mate. Hop on one that you like and ride it out. -Fuse |
|
|
|
I got my risers. USB 3 types. I plugged it in, then set my GPUs upside down, and they are all hashing (only 3 so far, I lent 1 to my brother in law.)
One got sick, so I dialed down the settings to 1145, 1500, but still using older BAMT 1.3. Haven't had time to upgrade to 1.5 but I'll do some testing soon as I already downloaded the image file.
Is there a thread for your other pools? or is it okay to discuss potcoin here? hehehe.
I haven't really made a thread for the pool network yet. I'll work on it soon. I've got a shitty situation on my hands right now, literally lol: I came home late last night to the plumbing in the house being messed up again. I spent like 3 hours working on it, snaking pipes, replacing wax rings on toilets that were bad, and the water in the house still will not drain. So I'm without water essentially, as there is no where for it to go. So give me a day or so and I'll create a thread for the pool network. In the meantime though, you can discuss anything here, mate. We do anyways lol. -Fuse |
|
|
|
Your nodes are fine, it's most likely Coin-E's nodes. Contact their support and see if they're seeing the transaction as pending. If they aren't seeing it, or it's been orphaned, you got the short end of the stick on the transaction, mate.
I agree with fuse on this. I know that when my wallet was on the wrong chain / node network, I was able to send and receive coins from coins-e. Fuse, I had to delete everything and start again and now I am able to confirm that I am on the correct chain. Here is a valid transaction to prove it: http://explorer.tagcoin.org/tx/?txid=6a8c12c39b6a832f2cee7afc392f02fc85310cf439bdee815d77ce502a521070The simplest way to check is to mine / send / receive and then confirm the transaction on the tag blockchain. If it's there, you're safe. If it's not, you're basically on the wrong side of the internet. Regardless, I've removed TAG from our array of coins that can possibly be mined on our pool until the rest of the pools connect / resync / etc, thus bringing us closer to a public BETA. I've been on the "right side" of the chain almost all the time, until recently when even though we've had less hashrate and plenty of wallet connections, we've shot ahead upwards of 100 blocks in minutes. Then the rest of the chain catches up or we resync backwards. Either way, it seemed like we hit orphans. I've been watching this for a while now. This is why I now believe it's not an issue with the coin code. It just doesn't line up. -Fuse |
|
|
|
Well now I have no idea where to start mining. Fuse is your pool still on down time? As you seem to be here and supportive alot I was hoping to join your pool. I suspect I'll need some help starting off.
Tagmining will not be mining until the fork/orphan/attack issue is resolved. I'd love to start it back up, but in the last 2 weeks I have had to pay about 850TAG back into the pool to cover orphaned blocks that were paid out before they were orphaned a day later. I just can't afford to keep up with that kind of loss. I would recommend Hashfaster, although everyone is suffering the orphan issue right now.
are my nodes wrong? these were pulled from page 117 on this thread i believe.
Your nodes are fine, it's most likely Coin-E's nodes. Contact their support and see if they're seeing the transaction as pending. If they aren't seeing it, or it's been orphaned, you got the short end of the stick on the transaction, mate. -Fuse |
|
|
|
I noticed some odd 'didnt send' issues with Blockchain last week also. I wonder if this also relates to our private discussions on the matter? Hrm.
68.7% of the time, I'm onto something, everytime.
You need to apply to the FBI with those detective skills... you'll get more bitcoin that way anyway. -Fuse |
|
|
|
For those of you talking about the tag exploits, Gox just released some interesting news on BTC. This may be relevant to TAG and the TAG example is just more extreme because of the way tag is setup. https://www.mtgox.com/press_release_20140210.htmlHuzzah! Good look, Bensam123. -Fuse |
|
|
|
|
Just a reminder that:
POT.CripToe.Com is still going strong.
Come give us a try if you're looking for a nice quiet place to park your miners.
-Fuse
|
|
|
|
|
Essentially that's where the profit in this manipulation lies. You push the fork, get your coins, trade on an exchange for something like BTC, then "unfork". Rinse repeat, and blame it on the coin's "POS problems".
BCX mentioned it when we had the first fork. He was going to use it to get back at BigVern. It would take a substantial amount of hashpower and an amazing understanding of the coin network, but I would think it is possible.
-Fuse
|
|
|
|
@ny2cafuse , what tagcoind version are you running? did you upgrade to 1.0.4?
Yeah. I installed 1.0.4 within the first hour of release. I honestly think there is some network manipulation behind this. If it isn't some sort of attack or manipulation, than TAG is really broke. I have never mined anything that went 2-3, or even 5 days like your pool, and had confirmed and paid blocks that just instantly orphaned. That doesn't happen unless you disconnect the nodes from the rest of the network, they run on their own fork, and then you all of a sudden reintroduce that entire node network back into the main chain. Essentially that's what you would do in a 51% attack. -Fuse |
|
|
|
|
I'm glad to announce the newest addition to my pool network:
KDC.CripToe.Com is now open!
Nothing fancy, just a solid 2% PPLNS pool. DDOS protection, fast payouts, etc... you know, the good stuff. We've already pegged a couple blocks, and payouts are working without issues.
When we pad the liquid funds a little, I'll start running a block reward- maybe in a week or so if we get mining support.
If there are any issues or questions, PM me.
-Fuse
|
|
|
|
|
FYI:
I have set the auto-payout to 0.1TAG for all accounts on Tagmining that had a wallet address. If you had a wallet address, you were just paid out. If you have not set a wallet address, please do so and set your auto-payout, or submit a manual payout.
I am a bit upset about the state of the TAG network right now. Now I want to get this completely clear: I am not blaming Mark or the TAG team. I'm not blaming the coin. I'm not blaming the pools. I'm not even blaming the hackers if it is in fact a network hack/attack. Actually... no, if it's hackers, screw them. I'm just peeved that people lost a decent amount of coin today, and I lost a substantial amount that I had to put back into the pool just to get payouts rolling again. I desperately want TAG to thrive and grow. I have been on board from the beginning and I've put a lot of time, effort, and money into supporting TAG and the TAG community.
That being said:
Tagmining will be remain in a non-mining state until these issues are resolved, and well behind us.
I'm sorry to all the miners that call Tagmining their home pool. I'm sorry that I couldn't do more to figure out what is going on. When the issues with the network are resolved, I will turn mining back on. Like I said in previous posts though, I really do believe the issues we are having are due to a network hack/attack, and not an issue with the tagcoin code. I want to make that explicit.
-Fuse
|
|
|
|
I created this list of nodes based on the IP of the pools, advertised here on the first page of this thread. This happened when I restarted the coin daemon and was unable to connect.
addnode=162.243.125.91
addnode=162.243.74.110
addnode=162.243.252.178
Ok, so I'm first on that list, and it seems that cryptopools.com is last. But interestingly enough, all three of your addnodes are coming out of the NYC2 Digital Ocean datacenter. Just an observation. Maybe get the botpool addnode on their to spread it around a bit. -Fuse |
|
|
|
1. This really is a bunch of hackers
2. We find them and torture them until they give up the coins and then slaughter them mercilessly. Boy that would be fun!
The thing is, I haven't made our pool public yet. Whilst we have been "discussing" it so to speak, the address isn't known. And we are also talking about coins mined, both days ago, and hours ago. One would suspect that were it hackers at fault, it would need to be a continuous attack and at the moment, I only see our own beta testing hardware connected to the stratum port. Or was the believe that the hackers would jump in, attack, leave... chaos. What, if any, addnodes are you adding to your wallet config? Maybe, if this is a hack, they are targeting specific nodes, and the nodes attached to them. I'm just spit-balling, but maybe we should try again to compile a list of all major pool nodes and static wallets to connect to. Perhaps strengthening the network node connections can prevent this from happening again. -Fuse |
|
|
|
|
NOTICE:
I am shutting down mining on the pool until this issue can be confirmed to be as either a problem with the coin code, or it's verified as a hack and there is a fix in place.
Payouts are now processing again. If you have account balances, make sure you do a manual payout or you set an auto-payout amount to help clear the wallet.
-Fuse
|
|
|
|
What's going on right now? The pool is offline, my unconfirmed balance has disappeared, and the blocks all show as orphaned... Missing about 40 tag right now.
Yeah, the TAG network is having issues again. I have posted about it in the main TAG thread. You're not alone, mate. I'm down about 400TAG right now that I will need to put back into the pool to get payouts started again. -Fuse |
|
|
|
Another 12 coins orphaned. Another 12 hours of work down the drain. Fuck this coin. You guys need to get your shit together.
I believe at this time that this is not a coin issue, but rather a stratum/wallet hack.I'm looking into it right now, but basically there is a miner or a group of miners that are using a stratum/wallet exploit to cause the wallet to stop syncing with the network, they inject their shares/blocks and then stop the attack. When it's all said and done, you're left with what looks like a fork and string of orphans. I believe this is essentially what you would do with a 51% attack, but on a more precise level. As I type this, we went from a liquid balance of 46 to -344 in a matter of minutes on tagmining. I'm guessing the other pool ops are experiencing the same issues. This isn't just happening with TAG. We are just being targetted more because it ends up at the top of the profitability list. See here: https://github.com/MPOS/php-mpos/issues/1072Initial observations are that this is coming out of China. If I have to go as far as blocking all Chinese IPs to test that theory, I will. But currently, I have suspended all payouts and mining on tagmining. You're coins are safe, and they are not being scammed. When I can resolve the -344TAG issue, and I can track who the hell is doing this, I will turn everything back on and the pool will resume operations. -Fuse |
|
|
|
Yes.
Okee guys. I orderd 2 asrock h81 btc pro moterboads with 2 pentium dual cores. And 2 gigs ram. 2 march i gonna order 2 psu and 4 hd 270x. And april if it works out the remaining 6 gpus for my mining facility.
Cant wait
NICE! Keep us updated, mate! -Fuse |
|
|
|
When will there be a network hashrate indicator? Or are there no plans for one, and why?
+1, this would be highly beneficial to troubleshooting orphan issues, and has been needed for a while. Mark, can the following code be used in the bitcoinrpc.cpp file: // Return average network hashes per second based on last number of blocks.
Value GetNetworkHashPS(int lookup) {
if (pindexBest == NULL)
return 0;
// If lookup is -1, then use blocks since last difficulty change.
if (lookup <= 0)
lookup = pindexBest->nHeight % 2016 + 1;
// If lookup is larger than chain, then set it to chain length.
if (lookup > pindexBest->nHeight)
lookup = pindexBest->nHeight;
CBlockIndex* pindexPrev = pindexBest;
for (int i = 0; i < lookup; i++)
pindexPrev = pindexPrev->pprev;
double timeDiff = pindexBest->GetBlockTime() - pindexPrev->GetBlockTime();
double timePerBlock = timeDiff / lookup;
return (boost::int64_t)(((double)GetDifficulty() * pow(2.0, 32)) / timePerBlock);
}
Value getnetworkhashps(const Array& params, bool fHelp)
{
if (fHelp || params.size() > 1)
throw runtime_error(
"getnetworkhashps [blocks]\n"
"Returns the estimated network hashes per second based on the last 120 blocks.\n"
"Pass in [blocks] to override # of blocks, -1 specifies since last difficulty change.");
return GetNetworkHashPS(params.size() > 0 ? params[0].get_int() : 120);
}
Along with the other code listed in that file that pertains to the getnetworkhashps function? If so, I'll create a pull request on github. -Fuse |
|
|
|
|
Show Posts
