Topic: [ANN] Litecoin - a lite version of Bitcoin. Launched! - page 391. (Read 1467278 times)
The real question is: Where's the exchange?
Current difficulty: 0.015625 = 67,108,864 hashes (statistical average) per block
at 10khash/sec that's, on average, one every 1hr 51mins 51sec (~112 minutes)
So you can work it out from there if you know your hash rate
(until the next difficulty change)
at 10khash/sec that's, on average, one every 1hr 51mins 51sec (~112 minutes)
So you can work it out from there if you know your hash rate
(until the next difficulty change)
Haven't found a block for a good few hours now. Hopefully there'll be a nice pool up soon with donation option!
I was going to put my hard ass > 1kh/s to try this new pool, but it seems Litecoin has frozen my computer. This is the second time. Using the latest windows client. No error messages, nothing else was running on the computer. Same comp was running fine last night.
Don't use the pool. It doesn't work.
I set up a VM on a different server, installed the same OS, compiled everything. Set it all up, and the same results.
Pushpool gives out work, everything looks okay, but no shares are ever found. I don't know if the target is messed up or what. It worked fine on the testnet, but on the litecoin mainnet, nothing.
I'm to the 12 hour of wasted time point where I'm just going to fuck it and give up. The RPC calls work fine. When you register, it uses an RPC call to verify the litecoin address (after sanitation of course)
So... sorry for now. I don't know if Artforz is following this thread, but I'm using his modified tbx pushpool. Should be the same from what I understand.
I was going to put my hard ass > 1kh/s to try this new pool, but it seems Litecoin has frozen my computer. This is the second time. Using the latest windows client. No error messages, nothing else was running on the computer. Same comp was running fine last night.
Typo on the worker page, it's _1 and password 1, not letters sorry.
Mee too... Stats empty at the pool.
http://184.107.145.244/
Litecoin pool. Consider it experimental right now , and toss a core on it and register real quick. It worked perfectly on the testnet. Now it's giving me a longpool every minute exactly, and I haven't had a share in 15 minutes from one computer. Stats are all reset and it is pointed to the production server.
Give me some feedback and I'll go from there.
Litecoin pool. Consider it experimental right now , and toss a core on it and register real quick. It worked perfectly on the testnet. Now it's giving me a longpool every minute exactly, and I haven't had a share in 15 minutes from one computer. Stats are all reset and it is pointed to the production server.
Give me some feedback and I'll go from there.
3 miners connected to this pool!!!
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.
The might be a good idea. But now that the coin is doing well, there's less need for a lot more locking anymore. Not sure if it's worth implementing it. I will consider it.
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.
at current difficulty (0.01562) it takes 18 hours and 38 minutes per block on average solo mining @ 1kH/s
it may be bad luck but I have a feeling I get less than that, too.
it may be bad luck but I have a feeling I get less than that, too.
When the real chain went live this morning I had to delete all the existing files in my .litecoin directory. Before I did that, although I had testnet=0 in the conf, I was on the testnet still. After deleting them (except the litecoin.conf of course) and restarting the client, I was mining on the real network.
Check if this is something as simple as that.
Check if this is something as simple as that.
I'm not new to this stuff unfortunately. I tried deleting everything except for the config file and redownloading. After catching up with the chain... nothing.
Does solo mining work for you?
Are you running litecoind with daemon=1 and server=1?
Are you running litecoind with daemon=1 and server=1?
I didn't have daemon on testnet and it worked fine. This is a linux dedicated server and I run litecoin on a screen. I added it, and same results.
Typo on the worker page, it's _1 and password 1, not letters sorry.
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.
When the real chain went live this morning I had to delete all the existing files in my .litecoin directory. Before I did that, although I had testnet=0 in the conf, I was on the testnet still. After deleting them (except the litecoin.conf of course) and restarting the client, I was mining on the real network.
Check if this is something as simple as that.
Typo on the worker page, it's _1 and password 1, not letters sorry.
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?
Typo on the worker page, it's _1 and password 1, not letters sorry.
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.
can't register
error message
Forbidden
You don't have permission to access /register.php on this server.
French IP and chrome
9 hours at ~1kh/s on three threads, only got 2 blocks and one orphan. is this normal or do I need to tweak my settings?
win7 on an intel quad@ 2.5ghz/core
win7 on an intel quad@ 2.5ghz/core
I'm on about the same statistics.
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.
coblee, can block locking be done via signed file so recompiling the client can be skipped?
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
Jump to: