Is anyone staking at the moment? I have one connection to the KTK network, but I feel like I forked myself, if I unlock my wallet I am staking every single block, that doesn't seem right

Are there any confirmed nodes with the main blockchain?
Current block # as of writing this is 1299510, I have 6 connections
Hm, are you sure that is the longest chain? I downloaded the chain file from the previous page of this thread, and it starts synching from block 151xxxx.
Did you sync from scratch, or which files did you use?
I couldn't get the new QT the dev posted to open, would always stall out, I'm guessing because my OS is 64 bit. Anyway, I checked the logfile and it appeared the DNS seeder in the new QT was working correctly before it stalled out on me, so I used the old QT and it connected to the correct chain. Dev verified I am on the correct chain by posting the current block number, the timestamp of when he posted the current block and when I verified was less than an hour, my block count was within 100 blocks, so I am 99.999999% certain I'm on the correct chain.
When you open the wallet, "help > debug window" will show the current number of blocks.
Which displays current number of blocks: 1242209, also when sync you can hover over the green tick bottom right
and see the amount of blocks you've downloaded. So be good if matches.
The only issue, with the old wallet is it has old nodes, which were replaced with dns seeder. But if it's working and
on the same chain should be fine.
I already did all that and the new QT refuses to open... the new wallet QT hangs as a grayed out box that says "Kryptcoin - Wallet (Not Responding) _ ◘ X"
If I do all the steps you mentioned but run the old QT instead of the new QT, the wallet opens fine, will connect and mints new coins, but I get the "WARNING: checkpoint too old" message... should I just ignore the warning? is there any way I can verify I'm on the correct blockchain and not a fork?
Well as of right now I'm at 1242298, so I'm going to guess I'm on the correct chain. I'll just use the old QT and ignore the warning then. Thanks for the help