so every thing is working is this correct  Allow me a few moments to finish reading over the finished whitepaper sent to me. I still haven't slept and have several messages left for me to address. As far as I know, there are still no issues aside from people who are asking for help via PM and people who are still using the old code. Bear with us. I haven't slept in nearly 36 hours, pushed out the update, worked my day job, and still have more to do before I can rest. |
|
|
|
It works for me  And Troll is sleeping, so why dont you send him a PM. I've been at work, and had other obligations earlier today. I have not slept yet. |
|
|
|
This is because devs changed pchMessageStart in the new version. It's like a magic fingerprint which clients use to determine if they're at correct network. Existing clients refuse your connection because you "talk different language". Devs: this is a huge mistake and you should never change pchMessageStart. Changing it is like waiting for a disaster.It's what wallet version and protocol version are for to determine wether the other side of p2p connection is at our version. Please change pchMessageStart back as soon as possible to allow new version wallets to join exieting network and sync. It's not possible to make a smooth transition into the new version with incompatible pchMessageStart as new wallets cannot join the existing p2p network. pchMessageStart should never have been kept the same as litecoin's. eventually it will be changed. I am working on an implementation of a bridge node to carry the network over that gap, essentially allowing the coin to run along 2 separate p2p networks to sync clients across the gap. That is not happening in the near future, but it will happen. 2 coins should share the same magic. |
|
|
|
Also note that every single file was scrapped and rebuilt from scratch quite some time after that. |
|
|
|
|
And now 16269. Come on, let's push through these last few blocks!
|
|
|
|
Hey TrollByFire, you in NZ? I checked out your timezone  Represent NZ lol! Negative. GMT-5. North Carolina, USA. And extremely tired. |
|
|
|
I downloaded new version. Now please guid me step by step. How to?
Step 1: Close the old wallet. Step 2: Back up your wallet.dat. Step 3: Extract the new wallet from the zip somewhere. (All the files.) Step 4: Open the new wallet. A bit more information would allow us to help you better. What problems are you experiencing? |
|
|
|
Mein windows wallet ist seit 5 stunden nicht syncron was ist zu tun?
If I understood this correctly, you're asking the same thing everyone else is. It's because the blockchain is slow. The difficulty algorithm will switch at 16300 and things will start moving faster. Until then, wait for someone to mine a block. Your wallet will show as synchronized as soon as it happens. |
|
|
|
I download the new wallet 1.1.0 -pre，but it still cant update the trade data ,it still stop to 16267~why??
I had update the litecoindark.conf~
16267 is the current height. wait for someone to find a block. Until we hit 16300 DifficultyShield still targets the old algo. But now that the new wallet/daemons are out, it's just a matter of time before things start functioning properly again. It seems like the difficulty is causing the blocks to be > 1 hour? Would this mean that the fork will be in around 40 hours? If so, that's a long time in crypto.. This depends entirely on how much hash rate gets thrown at it. If the price climbs high enough for the multipools to take notice, it'l go quickly. Otherwise, some of us will just have to keep mining at a loss to get us there. |
|
|
|
I download the new wallet 1.1.0 -pre，but it still cant update the trade data ,it still stop to 16267~why??
I had update the litecoindark.conf~
16267 is the current height. wait for someone to find a block. Until we hit 16300 DifficultyShield still targets the old algo. But now that the new wallet/daemons are out, it's just a matter of time before things start functioning properly again. |
|
|
|
question, does the new wallet cointains DifficultyShield?
and if, at which block will this happen?
Yes. 16300. |
|
|
|
Ok. Win32 build complete. A quick rundown of what happened for anyone interested: Straight gitian build broke. Hard. Tried to fix the base-vm image (trusty, amd64) and soon realized the issue was hardware, not software. Something happened to my build server at the worst possible time. Set up a temporary build server on a VM and started compiling by hand only to realize there were link issues due to host incompatibility. Recompiled all dependencies by hand, recompiled windows qt wallet and windows daemon by hand. Long story short, I had some unforseen issues due to a broken server that I will have to wait until wednesday to deal with. Here's the release: https://github.com/TrollByFire/litecoindark-staging/releases/tag/v1.1.0-pre1Windows users: Grab the .zip Linux users: Grab the .tar.gz and compile as usual. Please note that DifficultyShield makes use of C++11 features and requires a minimum GCC version 4.8.0 in order to compile, and 4.9.0 or later is recommended. Also note that I cannot upload this to the main website myself and/or tweet about it: This will have to be done by Robbert once he is awake/online. Timezones. |
|
|
|
|
Cloning from the staging repo is now 1.1.0-pre1. You need GCC 4.8.0 or better (recommend 4.9.0) to compile it. -std=c++1y isn't supported by the default GCC in debian 7.
|
|
|
|
|
Running a bit behind. Build server is giving some issues. Please bear with me.
|
|
|
|
very very nice, software development activities have been detected 3% premine has not been released doing quick git pull and build, this is exactly what has been happening with SYNC, congrats so far, very nice KNC miners are just around the corner you have till 4 QT but distribution is holding, you have a big one on your hands dont screw it up  git pull Already up-to-date. (from LTCD master) will try it tomorrow , no rush, thanks and talk soon Use staging repo. Rob's repo (official) is updated behind mine as we're on separate continents and timezones are hard. |
|
|
|
i only know about ,qt and exe  if you have a exsiting wallet make a back up of the wallet.dat. before updating already back up,..but after i download this file and extract,..what can i do next? basically you launch it then close it down make sure its not running and copy the wallet.dat back and start and it should sync up. Might take a few minutes to start syncing post-update. I'm also updating dns seed nodes. this will go away on its own and start working, just be patient. so can I use my same conf. file as well or will there be one included that is updated. same config. I have to stop posting now until finished. to many things going on at once. Will do a round of tech support Q&A posts afterwards. |
|
|
|
i only know about ,qt and exe if you have a exsiting wallet make a back up of the wallet.dat. before updating already back up,..but after i download this file and extract,..what can i do next? basically you launch it then close it down make sure its not running and copy the wallet.dat back and start and it should sync up. Might take a few minutes to start syncing post-update. I'm also updating dns seed nodes. this will go away on its own and start working, just be patient. |
|
|
|
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. after i download litecoindark staging,..so what can i do whit this file,...sorry i'm not familiar with this (blank) or or I have to wait until you update in website Bear with me, building final, verified windows wallets now. I'll post the minute they're uploaded. |
|
|
|
You should throw out a tweet for all the different updates once they go live. Such as when the Mac Wallet goes live and when the Windows wallets go live on the website.
Sadly I have to leave that to Rob. He controls the tweets. |
|
|
|
what freeware compiler is recommended to use?
GCC -- build deps are the same as earlier altcoins, you just need GCC 4.9.0 minimum. |
|
|
|
|
Show Posts
