Update your GCC.  Needs 4.9.0.  DifficultyShield makes use of C++11 features, next update will need C++14.  LTCD is going to diverge a lot from the typical copy-paste clone coins in the coming months.  You'll need an updated compiler.

Small error - Makefiles weren't properly committed.  Left out a compatibility define for boost and C++11, fixing and pushing.  (This is why I test before uploading.)

I'm still working on verifying the binaries.  Check the staging github for 1.1.0 first, as that's where I'll upload them (in just a few minutes, hopefully).  Binaries won't be available at litecoindark.com until Rob can upload them.

At this point, it's in the hands of the compiler.  Just making sure everything works and running tests.

Yes.

Just to clarify: We still need to get to block 16300 for the algorithm switch to happen.  Keep mining.  Push through these hard blocks for a chance and a cakewalk and some (once again) profitable blocks.

Update LitecoinDark v1.1.0-pre1 is being pushed and uploaded NOW.

This is a MANDATORY update!  You must update your client before block 16300!

LitecoinDark v1.1.0-pre1 is a pre-release build of LitecoinDark v1.1.0.  This update
includes the long-awaited DifficultyShield Core.

At its core DifficultyShield is an object-oriented abstraction and encapsulation of different difficulty adjustment algorithms.  This will allow for easier updates and modifications to the difficulty adjustment process in the future.  Note that it is currently in pre-alpha but due to overwhelming demand from the community, it is being released as-is, and is mandatory as it will cause a hard fork at block 16300 and will use the KGW algorithm for adjusting difficulty.  A more finely-tuned algorithm will follow at some arbitrary date in the future, but this will get the blocks moving again.

Binaries will be uploaded momentarily and this post will be edited to reflect their location.  If you'd like to check out the sources and compile yourself, you may clone the sources from https://github.com/TrollByFire/litecoindark-staging.  I will update this post and submit a pull request as soon as the binaries have been compiled, and will upload binaries to the staging repository as well.

Shortly afterward, the main website will contain this release as well, and you will note that the binaries have (as always) sha512sums that have been verified and signed by me.  Please do not run binaries from other sources not containing the proper signatures as we cannot guarantee that they were built from the proper source tree and have no way to verify what they may contain.

If you do not know what that means, make sure you get the downloads from our website http://litecoindark.com/ or https://github.com/TrollByFire/litecoindark-staging.

Thank you all for your continued patience and support.

Apologies, everyone.  I had family visit, so I was a bit delayed.  Hold tight, it will be here momentarily.

Update is ready.  1.1.0-prerelease binaries are being compiled now.  As soon as I can verify everything is working and sign all of the release files, expect an upload.

Target block is 16300.  I wanted to shoot for a higher block target, but as more miners pull out, I'm afraid it will take far too long to hit the original target.  This prerelease is essentially an object-oriented version of the Kimoto Gravity Well, with an expected update to a more refined solution somewhere in the future.  In the meantime, this will get the blocks moving again.

This is a mandatory update.  You must update before block 16300 to continue to work on the correct blockchain.


Binaries very soon now.  Sources will be pushed at the same time.

When you stop mining, you make the problem worse.  Time to hit the target block will increase.  I've rented and am throwing every ounce of hash power at it I can until the update is pushed and we can get over the bump.

I wont be able to publish until some time after 5:00 PM GMT-5 -- that will be the absolute earliest I can push due to work schedule.

Except if you read the OP it has already been updated.

You and everyone else do understand that there is one coder on this issue, right?  There isn't a difficulty problem.  There is a miner problem.  We're changing the difficulty algorithm to address multipools.  Right now we use the same difficulty algorithm Litecoin uses. Read: The code is identical in regards to difficulty.

Bottom line: It isn't broken, so "fix" is not the right word.  We have a better implementation coming, but we've already stated when it will be released.  FUD and trolling won't get it published any faster.

Apologies if I'm starting to sound harsh, but it does get tiring answering the same questions and comments over and over again.  Especially considering how little sleep I've managed to get since the launch of this coin.  DifficultyShield remains on track for release in 1.1.0-pre tomorrow.  Not tonight.  Tonight, I sleep.

Clone from the staging repository and checkout master or checkout the ltcd-1.0.1 branch (or litecoindark-1.0.1 tag) on your local clone.  Master branch is never guaranteed to be stable.  Releases are built from their own branch and tag.  Sounds like you're getting connections that you are dropping due to protocol version numbers not matching.  We didn't need to update the protocol version in 1.0.1 (nor has it changed in 1.1.0) and these changes were reverted and a newer code base will fix your problem

When a transaction hits a block that's 1 confirmation.  Each block found thereafter is an additional confirmation.  In short, yes.  Both problems, same cause, same solution.

Please read the last several pages.

I also want to go on record stating that before I was even officially a part of the team, I saw this coming and tried to make this the first priority.  Now we're stranded on multi-hour blocks, and I'm racing the clock to push out an update.  This is the community's coin, so we elected to start working on other things first.  Now everyone's rushing us to fix something that isn't "broken" tech-wise, it's broken greed wise.

I'm not getting paid for this; I do it to help strengthen cryptos as a whole.  If you intend to mine this later and can spare the hashes, please, do your part as well and mine.

Warning, slight rant incoming.

This is the very root of the problem.  When miners quit mining, blocks can't be found.  When blocks aren't found, transactions don't get confirmed AND difficulty doesn't get properly adjusted.  How many mined feathercoin at a loss when they the same problem?

You mine for profitability, but until the price goes up, it won't be profitable.  That said, the price isn't likely to go up until some blocks are found and the chain gets moving again.

This is why altcoins die. If you want to help the project, you don't have to donate.  Mine blocks.  Pre-release is coming tomorrow.  New difficulty algorithm is in the prerelease.  It will still need someone to mine to get it over the block target for the chain fork.

Late to the party?  I suggest reading through the thread.

Nope, just busy.  Troll on.

Two things:

First, "fix" isn't the right word.  It isn't broken, it's just outdated.

Second,