I'm seeing this:

2014-01-12 06:01:10   27571

Still 2 blocks behind the other pools.

EDIT- Looks like we're all on the same page right now... lets see how long that lasts.  Someone may have resynced the explorer wallet, or maybe Botpool is overtaking us.

There was a dev from the office that popped into this thread the last time we forked.  Might be the best choice if Mark is still in the air or away from the interwebs.

I wish I had direct contact info.


Mark was going on the block explorer yesterday... so I would bank on that, but if we have to race to another block, the other pools might prevail.


I wouldn't think it's anything nefarious, just really bad timing.  I don't think BCX would have anything to do with this.  I think this is something that all started with the orphan issues I brought up last week.

-Fuse

The fate of the world...

I'm not sure.  Can we verify what pools are on what chain right now.

I know Tagmining, Hashfaster, Cryptopools.com, and Cryptopool.it are all on the same block, but ahead of Botpool and the block explorer.

Botpool should be processing blocks faster than us, but they're not.  Not sure what the answer is at this point.

-Fuse

http://explorer.tagcoin.org/

It is currently 6 blocks behind the main pools.

Got a reply from HashCows support.  They have disabled Tag mining until the issue is resolved.

-Fuse

There's an API call that will pull the dashboard info from a MPOS pool, but everyone would have to have an account to call the API from, and we'd need to collect them all in one page somewhere.

As I write this, it appears HashCows is on a whole other chain.  Does anyone know who OPs over there?  We need to get them to pump the brakes.

-Fuse

EDIT- contacted HashCows support via email.  Hopefully they read it soon.

Hashfaster is ahead of all of us.

EDIT- now we're all ahead of the explorer.  Explorer is showing 557, and we're at 558(same as hashfaster)

Tagmining now matches the block explorer, but with a difficulty of 47?

I'm banking on the block explorer chain until this gets straightened out.  I'll be up as late as I can to try to ride this out, but the Modelo Especials I had at dinner are putting me in drowsy mode already.

-Fuse

EDIT- If I had to guess... I'd think we might be on another race to block XXX pretty soon.

Man... I've been thinking this whole time that the orphan issue was weird.

Explorer shows the last found block was

2014-01-12 05:22:27   27557

EDIT- I'm on board... Mark is probably still flying on his way to VA, USA.

Yes... I'm watching threads right now.  Will be watching the main tagcoin thread mostly, so if I don't respond here, you guys will know why.

-Fuse

Make one, and at the very minimum add that line.  Delete everything in the c:\users\(user name)\appdata\roaming\tagcoin folder ***EXCEPT*** your wallet.dat file and resync(reopen the wallet program).

I'm sure you know how to do this, but I want to make it clear for anyone who doesn't.

-Fuse

Set your .conf file with the following line:


Remove all the other addnode lines, and you should sync with my node.  You could probably do the same using the block explorer if you knew the proper address.

I wonder where the different forks are coming from  .

-Fuse

Confirming payment has been received.  Cards will be shipped Monday, and a tracking code will be provided.

Thanks,

Fuse

Posting a public sale notice for credibility and accountability.

I am selling Frankthechicken 3 x reference Sapphire 7950s for a total price of $750 shipped.  Confirmation to follow.

-Fuse

24Kilo, you might be interested, but I figured I'd ask openly in here just in case...

I would like to sell my 531145 Coinye for Earthcoins.  If anyone is interested, let me know.  Not sure what the conversion is, but I'll research offers.  Just PM me.

-Fuse

Just like the title says... 531145COYE for Earthcoin.

Make me an offer.  You send first unless you have stellar rep.

-Fuse

WTS 531145 COYE for Earthcoin, and Earthcoin only.  PM me with offers.  You go first.

-Fuse

Things are back to normal.

There was an issue with a false double payout being detected, and locking the cronjobs.  I've resolved the issue, and the pool should be working properly now.  I will be watching it through the day to make sure.

I will process the jackpot tomorrow in case there are any issues with the DB records.  I just want to make sure everything is squared away before I do the processing.  I hope everyone understands, and can wait a day longer.

-Fuse

FYI

There is something not quite right.  The front-end is running extremely slow.  I'm looking into it right now.  There might be some downtime today as I restart services and such, but nothing extended.

This also might be a DDOS, but the initial charts are showing otherwise.  I'll check with the provider as well to verify.

Jackpot might take a little longer to process today, so hang tight.

-Fuse



9:18AM PST : EDIT- MINING IS DISABLED UNTIL I CAN FIGURE THIS OUT.  Manual and auto-payouts will still be processing.

9:41AM PST : EDIT- MINING HAS BEEN RE-ENABLED.  I am still investigating the issues the pool is having.

I wish I knew people... wait... I know you, 24Kilo lol.

This stuff always seems to happen when I go to sleep.  Note to self: don't sleep anymore.

-Fuse