It is a bit dusty in here.
Has anyone got managed to get over the 7197 blocks?
If not, I'll changed the sources and added a checkpoint at Block 7197.
Currently looks fine, only "good" peers connected.
If ya want, give it a try.
Added a Pull request aswell on github -> https://github.com/YourDigitalCoin/YourDigitalCoin/pull/1/files

If anyone wants to compile for windows, go for it, i hate qt or mingw compiling

yeah, guess it is over.
But I still don't get a higher count from the 13k clients.
Summin is weired

dunno
started the payments again, if you want to keep on hole, set AP to 0

ATM i try to get this higher chain.
Would be nice if you could have a look in your wallet and gimme the IP and Ports of those, that have the 13k blocks.
I setup a different wallet, which connects only to those and I hope I will get the chain, atm i am connected to 4 but no blocks coming in

No clue.
Would be nice to get a block with the 12k transactions, to see what happened.
I could guess someone mined himself some blocks, as not many peers connected

For now I stop payments off the pool, till we have a word from dev team.
If someone wants a payout himself, leave me a message and I trigger it manually.

What is the actual blockcount your client has?

(Get it either with "getblockcount" in the debug console or Actual Block Count in the Information tab under Debug)

Fixed my Win Wallet with --rescan after all wrong block clients was disconnected

Edit again: Now 3 clients are connected with a startingheight of 12563

We need a Message from Dev

Found now 2 peers that show 12462

"addr" : "84.85.120.66:49391",
        "services" : "00000003",
        "lastsend" : 1398681154,
        "lastrecv" : 1398681154,
        "bytessent" : 9809,
        "bytesrecv" : 852,
        "blocksrequested" : 0,
        "conntime" : 1398680850,
        "version" : 70002,
        "subver" : "/Satoshi:0.8.6.2/",
        "inbound" : true,
        "startingheight" : 12462,
        "banscore" : 0


"addr" : "107.170.120.197:11010",
"services" : "00000003",
"lastsend" : 1398681159,
"lastrecv" : 1398681159,
"bytessent" : 351,
"bytesrecv" : 10340,
"blocksrequested" : 0,
"conntime" : 1398680813,
"version" : 70002,
"subver" : "/Satoshi:0.8.6.2/",
"inbound" : false,
"startingheight" : 12462,
"banscore" : 0


Interesting thing is, that both show startheight of 12462

@Dev: Anything you wanna tell us or just some guys messing around?
I will drop the connection to those on the pool for now

to which peers are you connected, that show 12340 blocks?

Quick & Dirty Setup, will see tomorrow or monday if all works okay, you can give me feedback aswell

http://188.138.32.6:8080/chain/YourDigitalCoin

Btw. Don't donate to the addresses listed there or on the pool, haven't changed em yet

@Dev: Change File Extension to tgz

As i mentioned earlier currently waiting for new maschines to go online to move the pool to a more stable location.
Currently the wallet stops working for some reason, therefore the pool open thousands of connections and gets no response and then no more ports are aviable
Tweaked some TCP stuff, should work better, otherwise I will have to killoff the wallet and restart it once a day.

Having some trouble with the current server ATM, gonna move the entire pool to a new location. All stuff will be saved and should be done till Sunday, you can keep on mining.

Don't have a blockchain URL yet
Confirmation takes longer as the blocks go in slower.

Will add another 25k for the donation. PM me the adress plz

nope, just some tweaks on frontend

Good point here. The other guy had about the same hashrate and claimed 600k in half the time you mined. I just don't wanted to have a negative wallet balance

To make some clearings.
He didn't lost 300k, as it was double payout in the database.
With an payout short after midnight of around 300k, which he received,after another 300k was dropped out, it is running smooth now.
To do some simple maths.

If he had all 600k, with a block reward of 500, he would have 1200 blocks on his own.
As far as I remember, the block height was around 4000 this time. So more as 25% should have been his blocks.
And this was just after the DB was resetted.

The "problem" is, new blocks are found in about 10 seconds.
Doing the Background stuff, sorting shares for blocks, payout etc. takes almost even as long as the finding of new blocks.
This is why the payment stalled, but nothing was lost, as I run it manually. About 2000 Blocks to pay.
Even when it is stalled, no need to worry, everything is saved.
Going to bed now and I hope it goes smooth over night, if not I will trigger the payout process manually again tomorrow morning.
Happy hashing

All is fixed. :-) Keep calm, the hashes rush up atm

Had to redo the DB, but now it should be stable. All Accounts and Workers were saved aswell as the rewards.
Page is http://ydc.hashes4.me

If there any issues, PM me

Thanks for the first users on the pool.
Currently it is a bit laggy, as the blocks fly in so quick. Stats are being calculated more often now, so should be stable in a few.