is there a gtx 760 kepler kernel code for this miner?
You can try tpruvot's |
|
|
|
|
There is not much room for improvement on blake coins like vanilla and decred.
|
|
|
|
What do you guys mine right now, ETH or vanilla?
None of the two. But if I had to choose one, it'd be vanilla (or decred). |
|
|
|
How many days to reach ROI?
anyone knows?
Mining bitcoin: never, as common sense would suggest. Common sense does help occasionally. However, in this case maths is more helpful. This is the simplified formula for SHA256 Bitcoin mining: ROI_limit = BTC_per_block * 1 THash * seconds_per_day / (Difficulty * 2^32) At the current Difficulty of 144116447847 this is 25 * 1000000000000 * 86400 / (144116447847 * 4294967296) or 0.0035 BTC/TH/sec/day (approximately) In other words: If you want to buy hashpower then you shouldn't pay more than 0.0035, otherwise you'll lose money in the long run. If you can offer hashpower then you should ask for 0.0035 or more in order to get an advantage over mining at the average mining pool. (Don't forget to take the appropriate fees into account.) After the next difficulty change (around Feb 19th in the evening, UTC) this ROI_limit will most likely be 0.0031 BTC/TH/sec/day. my thought was simpler and more widely applicable: if it was so simple to make money, everybody would do it and it would become unprofitable. hence you should look for some more exotic currency that are less known. |
|
|
|
How many days to reach ROI?
anyone knows?
Mining bitcoin: never, as common sense would suggest. Mining other coins can bring profit, though. |
|
|
|
http://fugue256.bit now available i wanted to reg fuguecoin.bit, but someone has regged it already ERR_NAME_NOT_RESOLVED besides, does this coin have any active exchange? |
|
|
|
|
I hate to say that, but my net annualized return is negative and getting worse: it will reach two digits in some weeks.
People stay away from this site full of scammers.
|
|
|
|
Mining from wallet, is the GPU memory minimum 2GB? Thanks in advance for any advice.
Can anyone answer this? If its 2GB minimum, I will order a new card. Right now when I start mining, it starts and then promptly stops. Not real sure as I have always mined with 2 GB or more cards, so maybe?,,,,, out of curiosity what are you trying to mine with? All I have right now is an old ATI 5850 1GB, but in market for newer card. Just wanted to get started mining until I got new card. I think I may need a 2GB card. I know ETH needs at least 2GB. Must be same for SIA. I went back through some of my older post and I did mine with a couple of 7790's at one point and they did work/hash and are 1 GB cards. Seems there may be something about the older cards like even the 6870's I have, seems they would not mine. I know the cores changed with the Radeon 7790's on up. So it may be the design of the GPU... Ill keep digging lol The mining algo doesn't use gpu memory (except for passing parameters to the kernel, of course). I guess you could do with a 256MB card as well. I see no reason why the miner wouldn't work on a VLIW card like yours (the final OpenCL code is very simple and compact). |
|
|
|
for me the 970 is the best for systems with one card... it start to be a problem with 2 in a closed box
why there is a problem with 2 cards? I guess cooling inside the case. But I assume you'll at least keep it open for mining, won't you? |
|
|
|
skip the 15.10, for me its not very ... finished, and the 16.04 LTS will come soon
True: go LTS for less maintenance and less issues (if you don't need to be on the edge). I went with LTS. Mint update frequency is not nearly as high as Fedora (don't know about ubuntu) but they do release critical updates promptly. I rfound Fedora annoying with their update frequency, especially the kernel which requires a reboot. So far i have nothing to complain about with Mint. All the software I use is available and the Mate desktop is configurable just the way I like it, I prefer it over Cinnamon. Well, mint is based on debian just as ubuntu and the two distributions have more than that in common. On a side note, I was wondering if there is a noticeable difference in hashing speed when using different gcc versions like 4.8, 4.9 or 5.0. |
|
|
|
skip the 15.10, for me its not very ... finished, and the 16.04 LTS will come soon
True: go LTS for less maintenance and less issues (if you don't need to be on the edge). |
|
|
|
|
Does mint finally have release upgrades?
Personally I'd go with ubuntu + lxde.
I have some pcs and servers which did more than 6 release upgrades with only minor issues (if any).
|
|
|
|
Too drunk.. Sorry guys. Trolling
You need a drunk detection lockscreen 😊 |
|
|
|
|
Unless some new coins come out using a broken implementation, there is not much to work on blake.
Some percent are possible thru unrolling and other tuning, but nothing special.
|
|
|
|
Hi guys, here is my github wallet fork: https://github.com/pallas1/joincoinIt already includes a fix for compiling with the newer libboost and the multiple wallet per machine fix. There are a couple more things I'd like to work on and let me know if you have any idea for improvement. But I will likely be unavailable in the next 2/3/4 days. did someone try that? did it work? any idea for enhancements? next week I may dedicate some hour to developing my fork of this coin, if there is interest. J X11 Joincoin server starting $ Feb 12 07:32:55.054 [warn] Could not bind to 127.0.0.1:9060: Address already in use. Is Tor already running? Feb 12 07:32:55.054 [warn] Failed to parse/validate config: Failed to bind one of the listener ports. Feb 12 07:32:55.054 [err] Reading config failed--see warnings above. on all but the first wallet, point tor to the first instance by running with -tor=127.0.0.1:9060 looks like that may have done the trick. I'll continue on and test more. I could eventually make it automatic: if it finds the port already bound, try to use it, instead of exiting. |
|
|
|
Hi guys, here is my github wallet fork: https://github.com/pallas1/joincoinIt already includes a fix for compiling with the newer libboost and the multiple wallet per machine fix. There are a couple more things I'd like to work on and let me know if you have any idea for improvement. But I will likely be unavailable in the next 2/3/4 days. did someone try that? did it work? any idea for enhancements? next week I may dedicate some hour to developing my fork of this coin, if there is interest. J X11 Joincoin server starting $ Feb 12 07:32:55.054 [warn] Could not bind to 127.0.0.1:9060: Address already in use. Is Tor already running? Feb 12 07:32:55.054 [warn] Failed to parse/validate config: Failed to bind one of the listener ports. Feb 12 07:32:55.054 [err] Reading config failed--see warnings above. on all but the first wallet, point tor to the first instance by running with -tor=127.0.0.1:9060 |
|
|
|
Hi guys, here is my github wallet fork: https://github.com/pallas1/joincoinIt already includes a fix for compiling with the newer libboost and the multiple wallet per machine fix. There are a couple more things I'd like to work on and let me know if you have any idea for improvement. But I will likely be unavailable in the next 2/3/4 days. did someone try that? did it work? any idea for enhancements? next week I may dedicate some hour to developing my fork of this coin, if there is interest. |
|
|
|
|
Show Posts
