the new version isn't even in the official repository.
where is the new version ?
Topic: [LTCD] LitecoinDark.com ★ Scrypt ★ Difficulty Shield ★ Multipool ★ Fast - page 296. (Read 368578 times)
September 16, 2014, 06:36:14 PM
where is the new version ?
September 16, 2014, 06:35:09 PM
I have no direct access to the primary github. All I can do is send a pull request, which I may have neglected to do in my sleepless state. I apologize for this, and am submitting the request now. As for the OP, I do agree that the staging repo should be listed, but again, have not even had the chance to address this with Rob.
I know that you are working hard, but please coordinate the communication better for the sake of LTCD.
Also, did you coordinate with exchanges and confirmed that they updated their wallets to the new version? I assure you that they don't read this thread and won't know that there is a fork if the new version isn't even in the official repository.
September 16, 2014, 06:34:17 PM
testing commit 411132e589a90d65c8bb7849694c47cbc9b3677b on ubuntu precise now
can't connect to official peers
September 16, 2014, 06:33:08 PM
so every thing is working is this correct 
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.This is all a hard business and we all really appreciate your work. You have proved yourself to be in the top echelons of crypto-developers in terms of hard work and community engagement.
I would also like to point out that it's a testament to the coin's community that the ongoing delay in blocks has not set the price crashing. If this were many other coins, the price would have dived and the investors would have fled. What has happened instead is that the developer is keeping us posted, the price is within 15% of its all-time high price and has been stable for 4 DAYS!!
Great work everybody, keep holding, keep giving advice and we will see a great future.
September 16, 2014, 06:31:24 PM
pchMessageStart should never have been kept the same as litecoin's.
This is true. The same goes for standard Litecoin's difficulty adjustment used for a late-2014 scrypt coin - never should happen unless someone have been living in a cave for the last year and wasn't up to speed with altcoins
.I see that you rolled back to original pchMessageStart in your fork (I was referring to the official repo which does have changed pchMessageStart). That's good. It is possible to change it, but it needs to be smooth (e.g. a transitional version which would accept both new and old values up until some block height after which it would only accept the new one).
Any reason why the new version isn't available from the official git repository? Yours isn't even listed from the first post.
This really creates confusion. You don't even need any external FUD if people can't get wallet to work. Source from original repo is broken, because the latest version includes changed pchMessageStart so this client won't connect to the network. Even if it wasn't broken, it would be outdated in just 27 blocks. The new version is on some outside repository which isn't even linked from OP. This is madness
Please update official repository or link your repository in the OP in a visible place. Otherwise how can you expect people to upgrade?
I have no direct access to the primary github. All I can do is send a pull request, which I may have neglected to do in my sleepless state. I apologize for this, and am submitting the request now. As for the OP, I do agree that the staging repo should be listed, but again, have not even had the chance to address this with Rob.
Also note that the "master" branch is not intended to be stable. Each release tree carries its own branch and tag. I can't expect them to know which repo to use, but even the official repo had a branch ltcd-1.0.1 and tag litecoindark-1.0.1 that was newer than the rollback and did sync properly. Maybe I should reconsider this policy due to the many who do not know how to checkout a branch...
September 16, 2014, 06:30:12 PM
I am not great at Logo Design....I work in newspaper advertising.... here is something I made in like 15 minutes just for kicks!
wow I like that looks good
September 16, 2014, 06:28:42 PM
testing commit 411132e589a90d65c8bb7849694c47cbc9b3677b on ubuntu precise now
September 16, 2014, 06:26:50 PM
I am not great at Logo Design....I work in newspaper advertising.... here is something I made in like 15 minutes just for kicks!
September 16, 2014, 06:25:12 PM
well we can help with the people that need help about installing the new wallet and answer their questions instead of pm you.
September 16, 2014, 06:24:59 PM
pchMessageStart should never have been kept the same as litecoin's.
This is true. The same goes for standard Litecoin's difficulty adjustment used for a late-2014 scrypt coin - never should happen unless someone have been living in a cave for the last year and wasn't up to speed with altcoins
.I see that you rolled back to original pchMessageStart in your fork (I was referring to the official repo which does have changed pchMessageStart). That's good. It is possible to change it, but it needs to be smooth (e.g. a transitional version which would accept both new and old values up until some block height after which it would only accept the new one).
Any reason why the new version isn't available from the official git repository? Yours isn't even listed from the first post.
This really creates confusion. You don't even need any external FUD if people can't get wallet to work. Source from original repo is broken, because the latest version includes changed pchMessageStart so this client won't connect to the network. Even if it wasn't broken, it would be outdated in just 27 blocks. The new version is on some outside repository which isn't even linked from OP. This is madness
Please update official repository or link your repository in the OP in a visible place. Otherwise how can you expect people to upgrade?
September 16, 2014, 06:24:42 PM
I am using recommended addnodes and built it fresh an hour ago on ubuntu precise.
September 16, 2014, 06:20:15 PM
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.
September 16, 2014, 06:17:28 PM
so every thing is working is this correct
September 16, 2014, 06:11:28 PM
It works for me 
And Troll is sleeping, so why dont you send him a PM.
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.
September 16, 2014, 06:10:23 PM
Seems like a recent commit as caused us to be unable to gain any connections. Using the official addnodes even
https://github.com/Litecoindark/LTCD/commit/5810c1c2e71ce1b6c26cc81d1b24cfd97f291d42
We are receiving disconnects as soon as we send the version message. Ill leave the wallet open to see if we pick any peers up but i cant reactivate deposits and withdrawals until it has connections
https://github.com/Litecoindark/LTCD/commit/5810c1c2e71ce1b6c26cc81d1b24cfd97f291d42
We are receiving disconnects as soon as we send the version message. Ill leave the wallet open to see if we pick any peers up but i cant reactivate deposits and withdrawals until it has connections
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.
September 16, 2014, 06:06:31 PM
Seems like a recent commit as caused us to be unable to gain any connections. Using the official addnodes even
https://github.com/Litecoindark/LTCD/commit/5810c1c2e71ce1b6c26cc81d1b24cfd97f291d42
We are receiving disconnects as soon as we send the version message. Ill leave the wallet open to see if we pick any peers up but i cant reactivate deposits and withdrawals until it has connections
https://github.com/Litecoindark/LTCD/commit/5810c1c2e71ce1b6c26cc81d1b24cfd97f291d42
We are receiving disconnects as soon as we send the version message. Ill leave the wallet open to see if we pick any peers up but i cant reactivate deposits and withdrawals until it has connections
Also note that every single file was scrapped and rebuilt from scratch quite some time after that.
September 16, 2014, 05:59:36 PM
Issue with the latest litecoindarkd from https://github.com/Litecoindark/LTCD not syncing ?
Unable to connect to peers. This code is broken. I am using recommended addnodes and built it fresh an hour ago on ubuntu precise.
September 16, 2014, 05:54:51 PM
Issue with the latest litecoindarkd from https://github.com/Litecoindark/LTCD not syncing ?
Its because you have to wait for Blocks to be found.
September 16, 2014, 05:52:23 PM
Can't we roll forward?
September 16, 2014, 05:41:06 PM
Issue with the latest litecoindarkd from https://github.com/Litecoindark/LTCD not syncing ?
Jump to: