Guys,
What are the alt-chains based on Scrypt, like Litecoin, Liquidcoin... ??
Thanks!
Thiago
Tenebrix, Fairbrix, Litecoin, Liquidcoin. |
|
|
|
Used to be at least 50; now it's more like 40 (probably because of Ozcoin's now-gone 10 LTC bonus per block.) But with every CPU I use for it, I get a minimum hashrate of 50KH/s, and a max of about 56.
Still, there are miners with 100+ KH/s in the pool I use, so I think that solo is a bad option for a lot of us.
What kind of CPUs are you using? The highest hashrate listed on the hardware comparison is the PS3 with 34. https://github.com/coblee/litecoin/wiki/Mining-hardware-comparisonIs that WiKi correct. I'm getting 7KHash/s on a Pentium D 3GHz and it says at Core2Quad Q6600 only gets 5KHash/s. Most of those benchmarks are relative to the original scrypt cpuminer by ArtForz. The current version of cpuminer is significantly faster, but not many people know about the wiki, and as a result the information on that page is now a little outdated. |
|
|
|
Alright folks, time for a version bump. Version 2.1.3- Support for extensions "midstate" (reduces network bandwidth usage) and "submitold" (used by p2pool).
- Smart handling of long polling failures: switch to short scantime if long polling fails.
- It is now possible to specify username and password in the URL, like this: --url http://username:password@host:port/.
- Added a --version option, and (finally) cleaned up the output of the --help option.
- The miner will now complain about non-option arguments, instead of simply ignoring them.
- Minor bug fixes.
The source code is, as always, available at GitHub. No binaries yet, sorry, I couldn't find diki on IRC. Windows binaries here. Brief note on the -s/--scantime optionI have seen people suggest various values for this option in order to reduce stales when mining in pools. The funny thing is that, to my knowledge, all Litecoin pools have long polling permanently enabled (which is good), and when long polling is enabled the scantime parameter is completely ignored. For this reason, the use of this parameter only makes sense when you are mining solo. |
|
|
|
It won't start when I enter the command I get -
matt@matt-ubuntu:~/litecoin$ litecoin-qt
litecoin-qt: command not found
matt@matt-ubuntu:~/litecoin$
Try prepending " ./" to the name of the executable: |
|
|
|
I'm using cpuminer right now to mine Litecoins. I'm behind a proxy and "minerd --help" doesn't bring up any options to specify a proxy.
What am I supposed to do?
According to the libcurl documentation, setting the environment variable http_proxy should do the trick. This seems to work well under Linux: export http_proxy=http://proxyaddress:port/
./minerd [usual options]
I don't have a Windows box to try it on, but I'm going to guess that set http_proxy=http://proxyaddress:port/
minerd [usual options]
will work. It may also be useful to know that some pools ( Pool-X for instance) allow mining on port 80. |
|
|
|
I have poolers it is running on a Q9400. But do i need flags for sse4.1?
No, to compile it just use CFLAGS="-O3", that's enough. |
|
|
|
So, me and a couple friends decided that we could mine in a private pool together.
Two Phenom ii X4, One X6's, One i5, and One i7.
I already own a ubuntu VPS and I have basic linux knowledge, can anyone give me an idea where to start? I understand PoolServerJ added Litecoin support, would it be best to try to use that? I just need pointed in the right direction.
Although the latest version of PoolServerJ advertises experimental support for scrypt-based chains, as far as I know nobody has managed to get it to work fine yet. At the moment I think you have two choices for the pool software: ArtForz's version of pushpool or p2k's ecoinpool. I don't recommend pushpool because it is currently unmaintained. I think ecoinpool is the way to go. |
|
|
|
Don't you just love that whole "OUR developer" thing? Just as if any of the socially awkward fan-boys who work on the ShortBusCoin are legit, educated programmers!
Wrong tootweasel, anyone involved in "development" (and by that we mean the completely incompetent and rather ham-fisted repackaging of other people's work with a few critically fucked up bugs added in, all released under an illegal copyright notice!) is an ass-clown just like their bitch-master. Oooh, your "developer"? Don't you mean the poor dumb bastard that you are currently ripping off code from and passing it off as your leet mad hakzor coding skillz? Those skillz make you, what was it again? Hundreds of imaginary dollars per hour? While living in your mom's rat-infested basement pleasuring yourself with lingerie ads? That kind of developer?
Listen, you have a whole cadre of believers (if two can be a cadre) on your own site. Why not hie your happy ass back there and have a group hug and tell yourselves conspiracy stories around the campfire about how aliens are real, tinfoil hats work, and ShortBusCoin is going to take over the world and allow you to implement your plan for world anarchy. Then Mommy can bring you all some warm milk and cookies and you can make shadow puppets with your secret decoder flashlights and marvel at how clever you are.
My Hero LOL That's the kind of post that could make you rich!  https://bitcointalk.org/index.php?topic=63092.msg743279#msg743279 |
|
|
|
I am no GPGPU expert, but I think ArtForz made some very good points in the following thread: https://bitcointalk.org/index.php?topic=45849.0CoinHunter could make his claims convincing by simply explaining how to address the GPU limitations outlined by ArtForz. |
|
|
|
Unfortunately a pure-Javascript miner would be too slow. For this reason, Vanderbleek decided to use Java instead. We were both working independently on the development of a Java miner back in November, but he stopped working on his version when I released mine ( https://bitcointalk.org/index.php?topic=52386.0), so that he could focus on the game proper. The source code to both miners is now available at GitHub. What exactly is the boundary of too slow? Even if it can do one share in one hour, that should be plenty for a site like facebook where people have it open all the time and has millions of customers. You all know I love efficiency. What I'm trying to say is that in modern browsers a Java miner can probably be 10x to 100x faster than a Javascript one, while retaining the same functionality (you can even access the internals of a Java applet using Javascript). I would hate to see a webpage use 100% of my CPU just to compute 20 hashes per second, given that there's a way to compute 1000 hashes per second. Pooler, for gamers who know very little about alt-coins/bitcoins, let alone mining them, what approach would you take
to get the gaming community to adopt Litecoin mining with spare CPU time?
I'm not exactly the gamer type (consider that my favorite games are X-COM and Master of Orion, and it's been a while since I last played them ), but I hope that Vanderbleek's project will set the example for other developers interested in Litecoin. The idea of mining coins and being able to use them in the game itself looks like a good one. On the other hand, there are many Flash/Java gaming sites that could simply use an embedded miner in addition or as an alternative to ad banners. |
|
|
|
All we need to do is to convince Vanderbleek to package the mining part of his game as a javascript library and open it up.
Unfortunately a pure-Javascript miner would be too slow. For this reason, Vanderbleek decided to use Java instead. We were both working independently on the development of a Java miner back in November, but he stopped working on his version when I released mine ( https://bitcointalk.org/index.php?topic=52386.0), so that he could focus on the game proper. The source code to both miners is now available at GitHub. I should be able to say something like: var LTCaddress = "LTCaddressForMyGame324yshkkss67"; <script src=" http://blah.net/ltcminer.js"> And my web page should generate LTC and feed it to the address above. Something like that has been available for two months now: http://www.litecoinpool.org/embedThis embeddable miner is discussed in the same forum thread linked above, starting here: https://bitcointalk.org/index.php?topic=52386.msg632047#msg632047 |
|
|
|
Auto payment threshold isn't working.
It seems to be working fine to me. Remember that automatic payouts are processed twice daily, at 11 UTC and 23 UTC. If you still think there's a problem with your account, please pm me specifying your pool username. |
|
|
|
It is coded in Qt and released under MIT license. It's currently only available for Windows, but Mac OS X and Linux compatibility should be easy to achieve if demand arises.
It's OBVIOUS there is "demand". What you're really after is donations /before/ it's done instead of doing it first and waiting for it to be worth something. Greedy much? I would like to point out that the OP never asked for donations. Also, it is not obvious that the author of a program can provide binaries for operating systems he does not use. |
|
|
|
Another bunch of scammers. Tried this for a couple of days, then poof, "Account has been suspended".
Nothing to see, move along, avoid this crap like the plague.
That message simply means that someone tried to access your account using invalid credentials and failed a certain number of times. For security reasons, in these cases the account gets blocked. Your miners and your balance are not affected by this, only the web access. You can regain access to your account by using the password recovery procedure ("Forgot password" link in the login form). A reactivation link will be sent to your email address. If you provided a fake email address that you cannot access please send an email to the address on the "help" page. I have now changed the message to be more descriptive. The next time something unexpected happens to you, please, ask the service operator before jumping to conclusions. |
|
|
|
I updated the program to work with the newest minerd shortly after I started the thread.
About the system tray minimization feature request, I think I'll get into it right now.
Cool. I was also thinking that it would be useful to have a command-line option to start the program (and the mining) minimized, so that users can set it up to autostart when the system boots. |
|
|
|
|
Glad to see that this project is back, I'm sure many users will appreciate it. (If you find the program useful, please be kind and donate some LTC to Matoking!)
I would like to observe that this new version correctly reports the number of shares even with the newest minerd.
I also have one feature request: would it be possible to minimize the window to the system tray?
|
|
|
|
That setting also defines how much a share is worth.
If you set it to N bits, miners will need to compute 2^N hashes on average in order to find a share.
So, for example, if you set N=16 you will receive twice as many shares than with N=17, but they will be worth half the value, so the result will be the same.
Bitcoin pools use a standardized value of 32 bits (i.e. difficulty 1); in the Litecoin world, however, no standard exists, although most pools use 16 or 17 bits.
Hmm, that seems a bit arbitrary, don't you think? Especially for the number of PPS pools that are out there. As a pool operator, I could set it to 18 and pay PPS on a lower volume of shares. As I said, there would be fewer shares, but they would be worth more. The value (in LTC) of a share must be computed taking into consideration the current difficulty of the network and the target you serve to miners (which is determined by the setting you mentioned in the OP). An example: suppose the current difficulty is 1. By definition of difficulty, this means that on average you need to compute 2^32 hashes in order to find a block worth 50 LTC. If you set a target of 17 bits, every share should be counted as 2^17 of those 2^32 theoretical hashes. So the PPS rate of a "2^17" pool will be two times the PPS rate of a "2^16" pool. Of course this computation is only needed for PPS. In a proportional system the value of a share is not important. |
|
|
|
No, you don't need to change it when difficulty changes.
That setting rewrites the target in the work served to miners so that they look for shares instead of blocks.
In practice, you should probably set it to something between 16 and 18. The lower the number, the more shares pushpool will receive.
Wouldn't the client submitting more shares impact a PPS pool's payout #'s? That setting also defines how much a share is worth. If you set it to N bits, miners will need to compute 2^N hashes on average in order to find a share. So, for example, if you set N=16 you will receive twice as many shares than with N=17, but they will be worth half the value, so the result will be the same. Bitcoin pools use a standardized value of 32 bits (i.e. difficulty 1); in the Litecoin world, however, no standard exists, although most pools use 16 or 17 bits. |
|
|
|
I'm trying to setup a private pool for my company and I have one question that I've seen discussed but not entirely in-depth.
The "rpc.target.bits" functionality is my biggest question. Do I need to adjust this manually with each difficulty change (since it seems to impact the # of shares submitted)?
Thanks!
No, you don't need to change it when difficulty changes. That setting rewrites the target in the work served to miners so that they look for shares instead of blocks. In practice, you should probably set it to something between 16 and 18. The lower the number, the more shares pushpool will receive. |
|
|
|
|
Show Posts
