[LTCD] LitecoinDark.com ★ Scrypt ★ Difficulty Shield ★ Multipool ★ Fast

[mothermole1]

On a different note.. The speed up last night in blocks seems to have stalled again. No blocks in 10 hours. Have the multipools been running rampant again with the difficulty?

[motorhead89]

i will read past posts....is there a bounty for a better logo???

[BitCoin Operated Boy]

dev - what you plan to do in the future for ltcd ?

the devs listen to the community and take our ideas and put it to a vote to see what we want

What many people want is a cryptocurrency using properties of BitcoinDark plus properties of Darkcoin and Litecoin.

For LitecoinDark to have any chance of competing with BitcoinDark it has to have all properties of BitcoinDark with at least some propertties of LTC and DRK.

[JCJr222]

i will read past posts....is there a bounty for a better logo???

Yes. If you look at the first page a bounty was added, but the amount is unspecified.

[mullick]

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

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.

Yes I know exactly what the pchmessagestart is. Thats why I didnt bang my head against a wall for an hour trying to find out why it wouldnt sync  

It is strange im not getting any updated peers though. Even if we did we are unable to communicate with the original network. So the only block we would get would be those which are mined by new clients. I suggest nobody update for right now. If you manage to get connections and mine a block on the new chain it may kick it off. But it may be invalidated later when patched

Fix:

Revert pchMessageStart back to the original. Ban peers the right way. By protocol version

[Matthaggie]

We have 1 billion invalid shares, and 700 million valid shares here at best pool....wtf is going on. I vote we skip this block

[mullick]

I vote we skip this block

lol 

[s1gs3gv]

Issue with the latest litecoindarkd from https://github.com/Litecoindark/LTCD  not syncing ?

[NxtSwag]

Can't we roll forward?

[Xircom]

Issue with the latest litecoindarkd from https://github.com/Litecoindark/LTCD  not syncing ?

Its because you have to wait for Blocks to be found.

[s1gs3gv]

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.

[TrollByFire]

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

Also note that every single file was scrapped and rebuilt from scratch quite some time after that. 

[TrollByFire]

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

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.

[TrollByFire]

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.

[voodoo1967]

so every thing is working is this correct 

[TrollByFire]

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.

[s1gs3gv]

I am using recommended addnodes and built it fresh an hour ago on ubuntu precise.

[IKnowBetter]

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?

[voodoo1967]

well we can help with the people that need help about installing the new wallet and answer their questions instead of pm you.  

[motorhead89]

I am not great at Logo Design....I work in newspaper advertising.... here is something I made in like 15 minutes just for kicks!