|
To expand upon what has already been said:
The blockchain is slow because the difficulty is outlandish. Bitcoin proper has a maximum adjustment when a retarget should happen. As a descendant of bitcoin, LTCD shares this limitation. However, when Bitcoin was first introduced, the concept of multipools was foreign, and so there was no infrastructure to protect the network in the case of a massive hash rate decrease. Recently newer altcoins have introduced alternative algorithms for calculating a proper difficulty retarget to deal with multipool coin switches, and they seem to work rather well. The two most popular implementations are KGW and DigiShield.
In my own testing, DigiShield seems to be a bit more responsive and accurate, and so I have been working on an adaptation of their algorithm to fit the architecture I'm designing for new updates. I have been removing difficulty calculation from main.cpp and placing it into the DifficultyShield class (which probably isn't the best name for it, but for now it's what it's called.) Since difficulty algorithm is being abstracted into OO classes, it will be trivial if, in the future, we need to create a new implementation or algorithm. Instead of hacking in V1, V2, V3, etc functions, we can simply derive from the base classes and only override the necessary methods. This also starts the process of removing some of the bloat contained in main.cpp.
I have no idea if this information is useful to anyone, but I hope it serves to clear up some confusion. The current (1.0) difficulty algorithm isn't "broken". It works great for Bitcoin. It works great for Litecoin. But it isn't the right choice for LitecoinDark, and I believe we have a better solution.
|
|
|
|
Wich bastards drop their ltcd, keep them people!!!!  Dev?  Just heard the developer ran away. So sad to see this happen again...  Figured I would just take the ridiculousness to the next level. I realize this was said in jest, but I can assure you, and anyone else who might be reading this: we haven't gone anywhere. |
|
|
|
Now this one I like better than any of the others. Submit it for voting, please! |
|
|
|
Client Update: v1.1.0.0-pre (Pre-release)Finally an update. This update addresses a few major issues. - The code was re-forked from a fresh litecoin tree and rebuilt (including litecoin's git history to properly show our lineage) - Sync issues were addressed by adding DNS seeds. Config files are no longer mandatory. - Icons were updated (for no real reason) to current oxygen icon set - Version numbers bumped The "unofficial" github was renamed to litecoindark-staging due to it no longer being unofficial. As an official developer, I make my changes to a local repository and publish to the staging repo whenever I feel I've reached the next target milestone. At which time, I submit a pull request to Robbert for review and merge into the official github. I do not manage the official github, nor do I have any direct access, but I prefer to work this way as I have complete control of the staging repository and Robbert can continue to maintain what gets into upstream. This release was pushed out quickly due to all of the sync issues that people were having. My local repository already contains various additional updates that will see a public launch in the next few days, and I am simply releasing this version for people to test and ensure that some of the bugs have been fixed. Once some distributed testing has been done, we will release version 1.1.0 proper. You'll note a message in the QT client stating that this is a prerelease build and that it should not be used for mining or merchant purposes. I would like to reiterate and specify this directly. Do not use this for mining or merchant purposes. It is a prerelease build and some things may break. Due to this, I will not be providing binaries, but if you would like to checkout and compile your own copy, feel free to clone the repository at https://github.com/TrollByFire/litecoindark-staging. Thank you all for your continued patience and support.
|
|
|
|
triple top! if we don't break through on the 4th try this could tank....we need to break the 3k mark ASAP!
Saw this a bit ago as volume collapsed and exited for now. Will keep an eye on it for sure but didn't want to risk it overnight. yep, I sold a portion off aswell as I thought it was going to dive, but its held so far...but it cant keep it up unless it breaks that 3k Buy support is building and only 5btc to push it over. Dev you have any news to push this over the line? I know its community based. News? Not much I haven't already said, but there's this:  |
|
|
|
When is road map coming out??
Go back and read the first post. We're doing a poll for feature additions. |
|
|
|
Non of these logos are good. I think dev team should purchase a professional logo from a professional logo designer not newbies.
To DEV team: Just find a pro logo designer from dribbble or behance.
This coin belongs not to us (the developer team) but to the entire community. I myself plan to do some graphical work (which I will submit for voting, the same as everyone else). |
|
|
|
To give an idea of what I've done so far before I push these changes for review by the team: - Re-fork Litecoin sources to start from a clean source tree.
- Update specs and network information to match LitecoinDark 1.0.1
- Update build dependency versions on Win32
- Added base implementation of adapted DigiShield clone on devel-1.1.0 branch (will not be published on master until thoroughly tested)
- Added DNS seed nodes (no more sync issues)
- Updated READMEs and documentation to properly credit dev team and give special thanks to other contributors and individuals
- Publish information on development Roadmap
- Core code cleanup and comments / documentation
- Started working on Doxygen code documentation
- Started working on Tor integration (largely untested, but a single connection & sync was performed)
So still very few major changes to the tree, aside from cleaning up the base code and inserting the difficulty algorithm changes. Major changes will be prioritized based on community input from the poll. Your feedback is greatly appreciated, and will be heavily considered before these changes are pushed to either github. |
|
|
|
|
Now that I've managed to actually get a little sleep, I should be able to push some of my changes into git. Thank you all for your ongoing patience.
|
|
|
|
Check gethup isuee for my problem Hello, i have download a wallet version feb. The wallet i had open worked untill my computer had an update and shut down. -THE DAY AFTER I OPENED THE WALLET AGAIN, AND IT MAKE AN OTHER ADRESS? WITH 0 Balance.? After that i saw some files that i have in the zip, "i realised that before my update the wallet didn't even make a wallet.dat or otherchain/block/log files." The wallets adress LVRqTkn5psXUVhw1edug3F5ToEzbLFnha5 I have an wallet.dat of 98kb and installed the newone 80kb, cause i saw it could be solved with a update. But i didn't see my coins shownup.i have a windows vista. Someone helped me and sayd to put in your old wallet.dat into the new area appdata. I did but nothing happend, nothing shows up. Wallet is synced - not jet resynced. Cause my wallet dind't saved the files into the map? my coins are stucked on a wallet i can't get to anymore? cause the wallet overwrite his self? Or there has never maked files from the wallet? cause my computer shutdown for an update, the wallet could not save the files that needed? So after opening it again it makes a new one:(? I have repeated again and again that i didn't see wallet.dat creations in the files or appdata. and after a reboot of my computer and after opening and instaling i did see some files but it whare not the files i have sended my coin. I think to understand that my computer has not saved the things that needed couse of reboot and update, the wallet wans't closed for days. Someone sended some coins to check, and i don't like that. http://explorer.litecoindark.com/address/LVRqTkn5psXUVhw1edug3F5ToEzbLFnha5is there anyway, i can solve this problem? Is there any developer that can check and deal in this untradable - Destroyed problem? uhm i don't know how to rescan, i have resynced and still nothings shows up dude send me your wallet.dat i will fix it LOL xD lol well i liked to gave you some really! if the problem can get solved Start the wallet with the -rescan option. See if that takes care of your issue. (quick and dirty method: make a shortcut to the litecoindark-qt.exe file in the same folder. Right click the shortcut and hit properties. In the "target" box, AFTER the quotes, type " -rescan" without the quotes. Make sure you include a space before the hypen in -rescan. hit ok, then run the shortcut. ) EDIT: Also I notice you keep mentioning a wallet version feb. If you mean February -- what coin are you even using? LTCD is only a week old. |
|
|
|
We think mining of the coin has a Super problem ! what's the formula for calculating diff ?
The diff is fixed at 1,599 at any network hashrate for one day .
This is already being addressed. Difficulty algo is the same as litecoin. This is changing in the next release. There isn't a "problem" with the algorithm, it was just designed before multipools became a thing. |
|
|
|
Hello,
So what's the solution to syncing problem with Wallet for Windows, please?
Add nodes to your config file, as stated in the OP. |
|
|
|
Hi,
Is there any reasons I am unable to SYNC my LTCD wallet. I have No Block Source available and there is no active connection to LTCD network.
See the reply I just posted. Could you, please repost the solution here. I have not got github account and don't want to register just to read one post about the solution to the bug. Thanks (I have got synchronisation issues too) At least read the github. You don't have to register to do that. Check your log for a version number. If it's 70003 you're on the wrong codebase. If it's 70002, you're either missing addnodes or you're having some other issue that I cannot troubleshoot without a debug log. Possibly IPv4/Ipv6 errors. I've heard mixed reports, but the only thing concrete I've seen is from people who were on the wrong version. The solution: Download the proper version. I don't know how to say that much clearer. I really wish I could help, but explaining things like this is not my strong suit, especially when the answer is nearly always the same thing -- Even more so when i've posted the exact answer one reply further up the page. I'm doing the best I can to help people here, but it's difficult when I'm not getting proper bug reports. |
|
|
|
this dev won't... or what is more realistic, doesn't know how to even fix their wallet to work on linux. It's been asked many times and no response or fix. How can any really expect any "features" from this coin? Aside from a hole in your pocket??
Quite the opposite. The wallet works great on my system. I run linux. If you clone the proper branch as I've stated over and over again or download the source tarball from the release page and compile, it will start working. Failing that, make sure you have addnodes and submit a bug report if nothing else works. no, not the opposite. I've tried the src from the OP as was as the hacker src. no blocks download. Then please submit a bug report, attach roughly last 200 lines of your debug.log. I've asked this several times. It works on my system. It works on the exchanges. It works on the pools. It's not a "linux" issue. After reviewing your log file I can state again, confidently -- this is not a linux issue. The network protocol version was bumped in the official repo in preparation of some changes that will require it. As I've stated time and time again -- this release was built from my repository at https://github.com/TrollByFire/LitecoinDark-Unofficial Branch ltcd-1.0.1 and tag litecoindark-1.0.1: You can view the "releases page" on my repository for a tar.gz of the sources at the proper branch and tag. I'm not trying to be cross, but I've stated this over and over again. You claim developer incompetence, and yet you haven't read the instructions. If I can help you further, please let me know. But trolling isn't going to win you any prizes here. As I've state over and over again... why isn't the dev fixing this? It doesn't work on my pool. The other 70+ coins do without this type pf issue. Who are you and what's your relation to the coin? I tried your version. There is no change. I'm not trolling, but I just want to know what the dev can't acknowledge anything. How much have you read? I am a part of the dev team. I'm even listed on the official website! My responses to you have been the dev response. I'm not fixing it because it isn't broken! The next release is going to incorporate features requiring a hard fork and client update. The protocol version has to be incremented. |
|
|
|
why cant i sync the blockchain with windows wallet?
Good question. Did you compile your own? If not, file a bug report. Attach logs. Will review as soon as I'm able. |
|
|
|
Who says that jl777 going to add this coin to supernet? Hype is over valuing this coin now!
No one says he's going to add it. I say we're going to apply in hopes that he will, but only after we've implemented some anon features. |
|
|
|
this dev won't... or what is more realistic, doesn't know how to even fix their wallet to work on linux. It's been asked many times and no response or fix. How can any really expect any "features" from this coin? Aside from a hole in your pocket??
Quite the opposite. The wallet works great on my system. I run linux. If you clone the proper branch as I've stated over and over again or download the source tarball from the release page and compile, it will start working. Failing that, make sure you have addnodes and submit a bug report if nothing else works. no, not the opposite. I've tried the src from the OP as was as the hacker src. no blocks download. Then please submit a bug report, attach roughly last 200 lines of your debug.log. I've asked this several times. It works on my system. It works on the exchanges. It works on the pools. It's not a "linux" issue. After reviewing your log file I can state again, confidently -- this is not a linux issue. The network protocol version was bumped in the official repo in preparation of some changes that will require it. As I've stated time and time again -- this release was built from my repository at https://github.com/TrollByFire/LitecoinDark-Unofficial Branch ltcd-1.0.1 and tag litecoindark-1.0.1: You can view the "releases page" on my repository for a tar.gz of the sources at the proper branch and tag. I'm not trying to be cross, but I've stated this over and over again. You claim developer incompetence, and yet you haven't read the instructions. If I can help you further, please let me know. But trolling isn't going to win you any prizes here. |
|
|
|
this dev won't... or what is more realistic, doesn't know how to even fix their wallet to work on linux. It's been asked many times and no response or fix. How can any really expect any "features" from this coin? Aside from a hole in your pocket??
Quite the opposite. The wallet works great on my system. I run linux. If you clone the proper branch as I've stated over and over again or download the source tarball from the release page and compile, it will start working. Failing that, make sure you have addnodes and submit a bug report if nothing else works. no, not the opposite. I've tried the src from the OP as was as the hacker src. no blocks download. Then please submit a bug report, attach roughly last 200 lines of your debug.log. I've asked this several times. It works on my system. It works on the exchanges. It works on the pools. It's not a "linux" issue. |
|
|
|
this dev won't... or what is more realistic, doesn't know how to even fix their wallet to work on linux. It's been asked many times and no response or fix. How can any really expect any "features" from this coin? Aside from a hole in your pocket??
Quite the opposite. The wallet works great on my system. I run linux. If you clone the proper branch as I've stated over and over again or download the source tarball from the release page and compile, it will start working. Failing that, make sure you have addnodes and submit a bug report if nothing else works. |
|
|
|
|
Show Posts
