im on 12134 with a diff of 15.45
You're on the right one, mate. |
|
|
|
Correct chain is blocks - 12133, difficulty - 14.49974591
Tagmining.com is on this chain now, and back up and mining away. |
|
|
|
Correct chain is blocks - 12133, difficulty - 14.49974591
Per Mark @ Tagbond, we are on the correct chain right now. Some of the blocks we pegged in the 12000-12100 range will probably orphan.You still using that PSU, or did you upgrade? After our convo, I thought about when mine was doing that with my 650w, and how with the insufficient voltage it was throwing all sorts of weird temps and speeds.
Or is this in the 2 card rig, meaning the second core on the second card?
No i mean my Main rig. I have 4 workers on my Main Rig with 1200 PSU. But my fourth miner keeps mining in Ghashes and then hey crashes. Total computer crash or just card crash in the miner? |
|
|
|
|
You still using that PSU, or did you upgrade? After our convo, I thought about when mine was doing that with my 650w, and how with the insufficient voltage it was throwing all sorts of weird temps and speeds.
Or is this in the 2 card rig, meaning the second core on the second card?
|
|
|
|
|
Resynced with Hashfaster, which appears to be the highest, unless there is a rogue. So be warned that you may lose some coins mining right now. I'm turning everything back on in hopes that we're on the right path, but we won't know for sure until the Tagcoin devs release the checkpoint.
|
|
|
|
Hmm... Now I know why the diff was dropping as everyone got closer to 12000
Yeah... sucks too. That fork was like 39 blocks off target. Anyone have correct nodes to add?
I'd recommend waiting for the new client with the 12000 block checkpoint. |
|
|
|
I'm watching the hashfaster pool. Same thing happened there. You are both claiming some of the same blocks after 12000 so is it another fork? Tagmining.com mining is down ATM. Looks like we went from ~11960 to over 12000 in one block. Looks like Hashfaster is on another all together. Waiting for resolution.
Yeah, I'm guessing we were on a fork that everyone though was the right fork, and *I'm not going to make an accusation against anyone* but someone with a lot of hashing power was pushing it along another route at the same point. To go 100 blocks over where everyone else was at would take at least 150MH, which is what Hashfaster and Tagmining were doing combined. Could be a multipool. |
|
|
|
|
Payouts and mining halted ATM. We went from ~11960 to ~12040 in one block. Hashfaster is showing another block number and difficulty right now. Waiting for the official client patch before anything resumes.
Caution: There might have been a rogue fork pushing the chain the whole time while the rest of us thought we were on the right chain. Be aware that this may jack a lot of stuff up. There is a lot of buy support on Cryptsy as well that may have been in place as a bull trap. Be warned.
|
|
|
|
|
Tagmining.com mining is down ATM. Looks like we went from ~11960 to over 12000 in one block. Looks like Hashfaster is on another all together. Waiting for resolution.
|
|
|
|
What kind of setup or rig has 550 MH/s of scrypt mining power?
also, whats a good guide to start some serious mining? Like, 4 video cards per computer or something?
Do you mean KH/s? A single HD 7950 should get you around 700 KH/s when mining scrypt coins. So with 4 7950s you should be able to get around 2.8 MH/s which is definitely a pretty serious setup for mining. what settings? I've never been close to that # with a 7950. Gigabyte WF3 7950 w/ F43 bios & modified .bin files from litecointalk forums( https://forum.litecoin.net/index.php/topic,6058.0.html): --thread-concurrency 24000 --lookup-gap 2 --gpu-engine 1130 --gpu-memclock 1250 --gpu-powertune 20 -w 256 -I 17 -g 1 <--- 640kh @ 77degrees with no additional cooling --thread-concurrency 24000 --lookup-gap 2 --gpu-engine 1130 --gpu-memclock 1250 --gpu-powertune 20 -w 256 -I 20 -g 1 <--- 701kh @ ~83degrees with no additional cooling With better cooling and tweaking the clocks, I could push more. |
|
|
|
It totally would be...
 |
|
|
|
we need some working pools up this is getting impossible to solo mine
There are pools up, mate. |
|
|
|
Maybe if pool operators could email the registered users when their pools were back up, then we'd switch back quicker?
I can't speak for the other ops, but I know I was a little too busy trying to keep things on the right track, mate. Posts were made about the pools being up. So... um... sorry... |
|
|
|
Sure would of been nice to have a stable pool to mine when it was low, low diff. The diff is already 15 in less than 24 hrs, FUCK!  Tagmining.com has been running since the difficulty was at around 1. |
|
|
|
|
I'm awake. Looks like we're still on the right fork, and we're rocking and rolling.
Thanks to all the miners that are keeping this going. 188 more blocks to go until we get to the checkpoint!
|
|
|
|
|
It's probably being overloaded a little right now. Tagmining is on the same chain, and is running at about 12MH currently.
|
|
|
|
|
Alrighty, folks... I'm calling it. I know I said I was probably staying up, but I just can't do it after the food coma I had today. We should be ok while I'm asleep. If SHTF, I'll resolve it in the morning.
If we do have a meltdown, or we fork on the pool, please PM me with our status so I know when things went south.
-Fuse
ALSO-
Pool veteran rewards and block finder rewards are suspended while all this is going on. They will need to be reevaluated when things get back to normal.
|
|
|
|
|
I've been trying to keep us going on the correct blockchain all night. I might be pulling an all nighter to make sure we stay on it. We are on the correct one right now, and what we make should pay out properly. But anything can change, so don't hold me to it. ATM, the pool is functional and working... so hash away!
If anyone needs to make sure their wallet is on the proper chain, "addnode=tagmining.com" in your tagcoin.conf file should square you away.
-Fuse
|
|
|
|
You obviously didn't read it very well, you didn't even bother to read the first post of this thread, or you would have seen that the fix kicks in at block 12,000 we are currently at block 10,913 so a long way to go at 4min per block. The dev should have made it block 11,000 but too late for that now.
Actually, when you think about it, it's a pretty reasonable target considering we still have people wondering what's going on. It's also Thanksgiving in the states, and there are probably a lot of people not around to catch what's going on. I've got miners on my pool that were asking me if they should keep their miners pointed at the pool when they left for the long weekend. But seriously people... just skim through the last 5 pages of this thread, and READ THE FIRST POST FROM THE DEV lol. |
|
|
|
Am I doing it right?
Technically, yes. Theoretically, no... not until we get to the hard fork. Pretty sure you're going to see a bunch, if not all, of that disappear, but I could be wrong. But if you are on the right fork, you're helping us get to 12000, so then it's a yes again. Would someone with more experience with a hard-fork situation like to elaborate on what happens to these blocks. Hazard, maybe? |
|
|
|
|
Show Posts
