I just checked in code to lock in block 4032 after diff change.
Please grab latest source. Windows client coming soon.
Windows client here: https://github.com/downloads/coblee/litecoin/litecoin-windows-client-40101.zipEveryone please update. Unfortunately twobits is asleep and can't help me build a windows daemon. And I only trust him to do that right now. So for those running on the daemon, you can stay with your current binary. As long as enough people are running the new build, we should be good against an attack. Thanks. To check to see if you are running latest client, getinfo should return version 40101. |
|
|
|
I just checked in code to lock in block 4032 after diff change.
Please grab latest source. Windows client coming soon.
Windows client here: https://github.com/downloads/coblee/litecoin/litecoin-windows-client-40101.zipEveryone please update. Unfortunately twobits is asleep and can't help me build a windows daemon. And I only trust him to do that right now. So for those running on the daemon, you can stay with your current binary. As long as enough people are running the new build, we should be good against an attack. Thanks. |
|
|
|
|
I just checked in code to lock in block 4032 after diff change.
Please grab latest source. Windows client coming soon.
|
|
|
|
The miner you are given doesn't have required files, keep on saying that libe is missing, this lib is missing ....
How many version or times, i have to download windows client & windows daemon.
Its seems more than 4-5 times downloaded & now dont even know which is the correct version & which i have to run. Hrm. One more try for the windows guys, this time linking static? I reported this problem earlier, you need to download libstdc++-6.dll and libgcc_s_dw2-1.dll and put them in the daemon's folder. I downloaded mine from mingw, it took some time, you might also find them on google (I don't know a trusted site except mingw). You need these 2 for the miner? Please upload yours to mediafire.com and I will add them to the miner zip file. |
|
|
|
Go back to using port 9332
9333 is the p2p port.
I switched to 9333 because I saw that the client was just not listening on port 9332, and was getting errors when I was trying to connec tto 9332. Still, even running the client with gen=1 does not generate, the client is on 0% CPU. I have had similar problems. Everything was fine with testnet, but problems happened after widows updated. Wonder if something with that is blocking it. The problem for me was a corrupt conf file, downloaded from the first post (probablly unix-style newlines). To fix, just create a fresh conf file with the values you need. coblee, please put this info in the first post or fix the conf file. My jsut sites their with 8 connections and says Catching up Downloaded 119 blocks, last d/l block was 2 hours ago. I have cleared it all and started over, and still get the same response, even after sitting for 15 mins, another on the same network is working fine. Download a newer client (find latest post by coblee with the client ... watch out, there were several released today). The first post of this thread will ALWAYS have the latest instructions and download links. |
|
|
|
Go back to using port 9332
9333 is the p2p port.
I switched to 9333 because I saw that the client was just not listening on port 9332, and was getting errors when I was trying to connec tto 9332. Still, even running the client with gen=1 does not generate, the client is on 0% CPU. OK, resolved, finally, at 5 GMT +2  The problem was I download litecoin.conf form the provided by coblee, with unix-style line endings. The client couldn't read them properly. So ... at what block# should we have a difficulty retarget? Diff will retarget at block 4032. It will be 4 times current diff. |
|
|
|
Go back to using port 9332
9333 is the p2p port.
I switched to 9333 because I saw that the client was just not listening on port 9332, and was getting errors when I was trying to connec tto 9332. Still, even running the client with gen=1 does not generate, the client is on 0% CPU. Definitely 9332. One reason maybe you are not caught up on blocks. Make sure you have the latest code. Call getinfo and see which block you're at and compare to http://blockexplorer.sytes.net/chain/LitecoinAlso call getwork and see if your daemon is caught up and giving work to your miners. |
|
|
|
Hey Coblee,
Can you please release a locked client on every retarget, starting 2016, then 4032 and so on?
At current difficulty, we have a lot of orphans that make the whole network loose a lot of time.
It's too easy for an attacker with even less than half the hashpower to catch up on his own branch where he gets no orphan blocks.
We need to prop up the security by locking in the retargets until the difficulty went high enough to make it unprofitable to forerun the chain.
Will do. I can only check in new source and build windows client binary. I need help from twobits for windows daemon binary. But I will try to release at every diff change. Will wait for 4032 for next release. |
|
|
|
grep "nHeight == 1500" src/main.cpp
(nHeight == 1500 && hash != uint256("0x841a2965955dd288cfa707a755d05a54e45f8bd476835ec9af4402a2b59a2967")))
Looks like git is correct. I updated a few minutes into the mining and got a change. Good to know. So, how about that difficulty change (or lack thereof)?
Already answered you. Anyone else confirm/deny my observation of difficulty not going up? Is the timestamp on the genesis block to blame here or should we be worried?
Difficulty won't go up until block 4032. The timestamp from genesis block was more than 3.5 days ago. |
|
|
|
Anyone else confirm/deny my observation of difficulty not going up? Is the timestamp on the genesis block to blame here or should we be worried?
Difficulty won't go up until block 4032. The timestamp from genesis block was more than 3.5 days ago. |
|
|
|
Is it "version" : 40100? Not getting any new code from git pulls.
Sorry, I did not change version number. Run this: more src/main.cpp | grep "nHeight == 1500" Does it give you something? If so, you have the latest code. |
|
|
|
Sorry guys. I locked in a block that was later orphaned. D'oh! It's too chaotic. I've checked in the fix with the right hash. If you compile from source, please grab latest and recompile. Windows client and daemon coming very soon. |
|
|
|
Coblee, how many LTC did you give BCX so he does not attack this chain !?
How come he attacked Failbrix but he does not attack Litecoin !?
Maybe you refused to bribe him with FBX but now did bribe him with LTC !?
Thanks !
I didn't give BCX any coins. I don't have any to give. He says the attack on fairbrix was just beta testing the attack on SC2. Since the fairbrix was new and had no exchange, it really didn't hurt anyone. I don't bribe people. |
|
|
|
coblee, any idea why almost all my proof of work are false? I understand orphan blocks, but what's with all the false proof of work?
Afaik, when minderd shows 'FALSE boooo', that just means that particular hash was for an already found block. It just mean that by the time your miner reported a block, someone else already reported a block to your litecoind and it's already stale. |
|
|
|
Getting orphans just fine even with the patched source. The patched source will not prevent orphans. Just prevents someone from doing a 51% attack from block 3 and releasing it to orphan EVERY single block from block 3 onwards. |
|
|
|
|
Show Posts
