Typo on the worker page, it's _1 and password 1, not letters sorry.
Still something wrong with stats - I've been mining for 10 mins but no stats (still 0 active workers), then it logged me out How many shares did you submit? Stats aren't updated, because there are not submitted blocks. I've had 3 computers hashing at this for an hour and no shares... somethings wrong. I recompiled everything, even switched back over to the testnet but no one is on it for me to see if it still works there. All I did was remove testnet=1 and added the nonce and stuff and restarted everything. I updated to the latest versions of litecoin, nothing. I don't know what the difference between testnet and litecoin main is, but the pool isn't working. Anyone smarter than me I'll share a % with you if you can help me get this running. I don't know what to do from here though. I've recompiled pushpool from artforz and litecoin with no additional positive response. Does solo mining work for you? Are you running litecoind with daemon=1 and server=1? |
|
|
|
coblee, can block locking be done via signed file so compiling the client can be skipped?
I suggested this over IRC but got a lot of pushback. My suggestion was that I can use the alert system to send a message to all clients with a new locked block. But people were worried that I might abuse this privilege, so I didn't do it. Another option is to be able to modify the config to add new locked blocks. So I can publish to the forum what I considered a good block hash and everyone can add it to their configs. Problem with this is people will make mistakes and cause their clients to do a wrong lock. Or they will attempt to do their own locking thinking that that would protect them. And this might cause them to fork their own chain. So it could get pretty messy. So for now, we will stick with new source/compile/binary. |
|
|
|
Here's your first LTC donation:
5ea309a5ef53d2caef2806a66644ce9f3beeea094c58fe06026e8225799c804c
Thanks  Yup, sent you something too: 02d72cdb6ca1a5964123848934e97fd60358cc3e6614b38d91848105c3dc2638 |
|
|
|
Auto update is unsafe, because i (or someone else) can push out a malicious update.
So.... Is this one a malicious update?  It's better if each user decides for themselves whether or not to upgrade.
Should I upgrade? Check my past history and see if you trust me. If you do, then you should upgrade to the latest binary. I would suggest that everyone build their own clients from source if they are able to. And you can easily see from the source that nothing malicious was added to the bitcoin code: https://github.com/coblee/litecoin/commits/master |
|
|
|
any chance the next client can have an auto-update capability? Auto update is unsafe, because i (or someone else) can push out a malicious update. It's better if each user decides for themselves whether or not to upgrade. |
|
|
|
Client doesn't connect.
Does anyone know a node I can add?
look at your debug.log file and see what's going on. |
|
|
|
Your network hash rate is increasing, in 10 minutes you have gone from 1.5 Mhashes to 2.5 Mhashes, you are under attack.
Where do you see that it went from 1.5 to 2.5? After the difficulty increase, getinfo showed me 2.5 after 120 blocks. |
|
|
|
Cool, I will pull it down. Majestik over at SC has made the mention, he is the only one with enough horses to do it. He knows he cant hang with BCX though  What kind of attack do you think they can do? If it's a "build a longer chain in secret" attack, we won't even notice it, right? If we notice an increase in hashrate, it's just someone trying to mine legitimate blocks, right? |
|
|
|
Cool, I will pull it down. Majestik over at SC has made the mention, he is the only one with enough horses to do it. He knows he cant hang with BCX though We're finding a block about every 7 seconds now. It will take about 2-3 more diff increase for things to match up. |
|
|
|
@Coblee,
It appears that someone is trying to 51% you, I saw the jump to 1.5 Mhashes in a matter seconds so I brought 600K online to make it that much harder.
Actually I don't think anyone is. The jump you see is because there were too many orphans before and it was underestimating the real network hashrate. After the diff increase, it's more accurate now. |
|
|
|
I am mining very smoothly , do I need to update? 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. If you don't want to get wiped out by a 51% attack, you should update. Just stop and the start the new client. You will be down just a few seconds. Coblee, Not meaning to be picky but you cannot update against a 51% attack. You can hard code the lock in, but that is it. The only thing that protects against a 51% attack is hash power, that's it. With your lock in you can back to a restore point basically after the 51% attack has concluded or enough miners update with a client that recognizes the proper fork only. ~BCX~ Yes, I know that. But updating to the latest lock will deter an attack that was starting on a block before the lock. So it does help. And when that happens, the chain will fork. So if enough miners get the latest code with the lock, they will be on the proper fork. And I expect eventually pools and exchanges to be on the proper fork, so there's no reason for a miner to not update their client and stay on the attacker's fork. Since we know that hash power protects against 51% attacks, right now there's way too many orphans due to the difficulty being low. So if an attacker is building their own chain, they only need ~900mhash/s to succeed even though our current network hash rate is much higher than that. So that's why I will keep doing the locks until the difficulty catches up. |
|
|
|
So how often are you going to lock in blocks? Every retarget will get a bit out of control I'm thinking.
I will lock in the next retarget 6048 and then I will go to sleep and maybe another lock in when I wake up. We'll see. Once the difficulty catches up to the network, it would be harder for us to get attacked. |
|
|
|
I am mining very smoothly , do I need to update? 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. If you don't want to get wiped out by a 51% attack, you should update. Just stop and the start the new client. You will be down just a few seconds. |
|
|
|
|
Sp0tter, thanks for adding Litecoin. One suggestion I have is can you add the difficulty column in the second table? Not sure why it's in the market table. That way coins without an exchange will also show current difficulty.
|
|
|
|
|
Show Posts
