I've been nothing short of accepting of your incessant trolling and FUD, passed along the link to your facebook page to Robbert, and have continued listening to the garbage trolling you post in hopes that you might at least make me chuckle.  In this task, you've failed miserably.  I sincerely hope you don't have any issues that I could have helped you solve.  Welcome to the ignore list, buddy.

If you don't want anything to do with this coin, then please, and with all due respect, GTFO.

This is what happens when a large multipool picks up a new coin.  Especially one without an advanced difficulty algorithm (asymmetric).  The pool pushes the hash rate "to the moon" and when the difficulty jumps and the coin is no longer as profitable to mine as other coins, it switches leaving the small miners to fight with an outlandish difficulty.  This has already been stated several times in the thread, and if you'd like, you can file an issue on the github.  That said, we're already very aware of it, and are working hard to get a better difficulty algorithm in place.

Thanks.  Due to some of the supportive posts you've made, I know you're being sincere, but as an aside, whenever I see the words "Nice work Troll" I always have to do a double-take to figure out if they're talking about me, or if someone's trolling, haha.

Give it a few minutes and it should show up on the explorer.  Right now we're fighting against a multipool for difficulty adjustment causing blocks to slow down.  Not sure if this is the problem, but if it is, it's one that can be solved by waiting.

See the reply I just posted.

Please see the issue on the github I linked earlier.  Update and attach a few hundred lines of your debug.log.  Let us know what OS you're running as well.

If there are any other users with issues, please check https://github.com/TrollByFire/LitecoinDark-Unofficial/issues to see if it has already been reported; if not, feel free to file a bug report.  I'm currently being swamped with everything from the difficulty jumps and the sync issues, to feature requests.  File an issue at the given url and we'll assign priorities to them and take care of it asap.

Got the logs, have reported the issue in the unofficial github.  Just as soon as I get the chance I will look it over.

I've almost finished getting my local repository cleaned and sorted out.  Will update and push to github as soon as that happens.  That will give me something much cleaner to work with in the future.

Bounties are being filled by the original dev.  Send him a PM here with a link to the wallet.  We'll review it and he'll get back to you.  Send him your LTCD address as well.  Thanks.

I would still like to see the last 200 lines or so from your debug.log.  Otherwise, I have no idea what's going on and can't help.

Make sure you're using the source code released with the binaries (the tarball) and pastebin that log.  I'll look at it as soon as I can.

I can't speak for anything regarding the original release or code base, and still have a lot of work to do in this area, but the repairwallet RPC method may not have existed when the codebase was forked. (I haven't gone through all of the RPCs yet.)  This should probably be filed as an issue on the github.  I'll try to get it merged in asap.  Still a few things that have slightly higher priority though.

I haven't heard any "hidden blocks" accusations.  It would be awfully hard to hide blocks... If you're referring to the multipool that keeps hammering us, I'm working on fixing the difficulty adjustment algorithm to help keep transactions fast when the multi drops off.  Whatever FUD, trolling, or any other accusations are being tossed around, it doesn't matter what kind of statement we give, the trolling will continue.  No matter how many times we state that they are "entirely unfounded", no matter what proof we can provide, (frequent updates, block explorer, transparent premine (of which I have no access to)) some people will continue to remain negative, greedy, and persistent.

Besides, I trust the community to be able to spot a troll when they see one.

Pardon my curiosity, but a statement regarding what? I've been busy tweaking difficulty adjustments and figuring out where to fork all day.  Have to do something about that multipool...

Honestly not even watching the markets.  I hope it has been a profitable day for everyone, but I'm a coder, not a trader.  Good luck.

Please remember that trolls will be trolls as long as they're being fed.  If the guy isn't interested, he'll move on.  The fact that he's not interested, and still posting just indicates that his motives lie elsewhere.  (Either just trolling, or something else.)

Also, if it was someone involved in the development of the coin with that kind of hash rate, why wasn't it being used prior to the first halving...  Logic, people.

addnodes in config file?

checkout tag litecoindark-1.0.1 -- master branch is broken.  Either that or check releases page on my github and grab the source archive (.tar.gz)

Several good suggestions for future additions from the community.  Please keep them coming.  

I saw the facebook page, not sure if anyone else on the team has yet.  I'll bring it up.  Don't worry, we haven't forgotten about anyone, we've just been extremely busy.