Who wants to make Litecoin 2.0? =P
There's no need to reboot the whole thing. We could just change the algorithm starting from block N. but i think this could split the chain and make one with "old clients" and one with "new" ? Of course people will have to update their clients and miners, but if the transition is planned out carefully there should be no risk. Once the software chain knows about the switch, it can handle it automatically. There's support for this in the protocol. EDIT: I think this discussion should move to the dedicated thread: https://bitcointalk.org/index.php?topic=64239.0 |
|
|
|
Who wants to make Litecoin 2.0? =P
There's no need to reboot the whole thing. We could just change the algorithm starting from block N. |
|
|
|
Now, that the truth has been apparently settled. I still don't feel scammed at all for mining LTC. If I were to start mining Solidcoin on the other hand I would. (I don't feel scammed for mining SC 1.0, however.)
To me, this is all just a bunch of noise. Lets just plan on changing the algorithm (or not).
+1. Couldn't have said it better. |
|
|
|
I talked to the author on IRC, this is a port of the Java miner. I guess it is so slow because the Android JVM is not as powerful as the one available for PC. It would be nice to see a port of the C miner. p2k managed to compile it for the iPad 2, and got about 0.85 khash/s on two cores. |
|
|
|
Hey, interested in Litecoin's web miner in particular, since I'm running one of Hexxeh's Lime builds of Chromium OS. (.5 seconds from Closed Laptop to Working Laptop, mostly.) Anyway, it does have a version of Java on it that it finicky with Java Web Start, but applets should work fine, which is why it's bothering me why it isn't working. Where would be a good jumping off point to find out where the holdup is, what can be done, and possibly porting the original C miner to the all-powerful Native Client, since Chrome has ties directly into hardware?
What version of Java is it? |
|
|
|
Im using the same program on all my comps , the only difference is the 64-bit shows hashes but my others dont , all my processors are 64-bit but only one has 64-bit OS
Correct me if I'm wrong... isn't a 64-bit OS needed to run 64-bit applications? |
|
|
|
Version 2.1.4- ~2% speed increase for 64-bit systems (excluding K8-based CPU's, i.e. Athlon 64's and older Opterons).
- Support for SOCKS 4/5 proxies via the new --proxy option (see README file).
- Username and password are no longer mandatory (I'm sure p2pool users will appreciate this).
- Support for building on Mac OS X (see README file).
The source code is, as always, available at GitHub. Binaries will be available soon available here.
|
|
|
|
Thats normal, that message should be popping up every 10 seconds or so
More precisely: - About ten seconds when using p2pool.
- About two minutes and a half, on average, when connected to a classic pool.
- Never when mining solo.
no it doesnt show my hash rate tho
I assume you are using Scryptminer GUI. Does the hash rate show up in the top left corner? Also, what is the hash rate reported by the pool? |
|
|
|
I've been having a bit of an issue lately. When I'm looked in, I get logged out whenever I try to view the Stats page. Any ideas?
All of the other pages work fine, and I remain logged in.
Cheers
In theory you should only need to re-login if your IP address changes, or if the session expires (after a week). Have you checked that your browser is not using a cached version of the Stats page? |
|
|
|
How do I modify the .BAT files to allow me to mine solo?
I know it's port 9332, but what should I put for the url, username, and userpass?
You should use the values of "rpcuser" and "rpcpassword" from your litecoin.conf file. For the URL you should use the IP of the machine that is running litecoind; if you're using just one machine, the default value ( http://127.0.0.1:9332/) should do. Where's the litecoin.conf file? Do I have to create this? I've been pool-mining just fine. You need to have the Litecoin client running if you want to mine solo. https://bitcointalk.org/index.php?topic=47417.0(coblee's post contains all the info about the litecoin.conf file.) |
|
|
|
How do I modify the .BAT files to allow me to mine solo?
I know it's port 9332, but what should I put for the url, username, and userpass?
You should use the values of "rpcuser" and "rpcpassword" from your litecoin.conf file. For the URL you should use the IP of the machine that is running the Litecoin daemon/client; if everything is on one machine, the default value ( http://127.0.0.1:9332/) should do. |
|
|
|
But the graph in http://pool-x.eu/net says 67.2 % litecoin mined by unknown [img] 51% attack going on  ?? The total network speed is probably computed using the "getnetworkhashps" RPC call, which can be very inaccurate after difficulty retargets, even when the difficulty doesn't change significantly. In addition, the 15 MH/s miner that made an appearance at litecoinpool.org a few days ago has now (quite rightly) switched to solo mining. By the way, I have talked with this miner, and I am now pretty sure that this is neither a botnet nor a GPU farm. |
|
|
|
The 2.1.3 version of poolers miner doesn't seem to start for my with ScryptMiner-GUI either, any ideas?
This should be fixed in the GitHub repo already, we just have to wait for the next binary release. |
|
|
|
right it looks like 7,7kh/s  The comma looks like a decimal separator to me. I read "7,810 kH/s". I don't know where you're from, but as far as I know, at least in English-speaking countries, the decimal separator is the period (.), while the comma is only used as a thousands separator. |
|
|
|
How many computers do you utilize for your 60kh/s?  It's 4 PC's: a Phenom, a Sempron, an Athlon 64 and an old Core 2 laptop. and pooler, you should really fix your displayed hashrate on your pool website. It shows a 1000times smaller number then it should... What hashrate are you referring to? Everything looks fine to me. |
|
|
|
how come that one day minerd was saying 100% accepted (shares?) and now it is around 99.6% ? What does it depend on?
That's the ratio of valid shares to submitted shares, and roughly speaking it can be considered as the complement of the stale rate (although it also takes into account invalid shares, if there are any). The acceptance rate depends on network latency and on the speed at which the pool server handles incoming requests. As a rule of thumb, it should stay above 99%. |
|
|
|
Thanks for this, I had a feeling that 10KH/s was a little low on a Quad Core i7.
What is a reasonable expected MH/s for an i7 950 @ stock (3066MHz) using 6 threads?
You tell me. Everybody is invited to contribute benchmarks of their processor in the cpuminer thread. |
|
|
|
|
Show Posts
