 Show Posts
|
|
Pages: [1] 2 »
|
|
Даш конечно жестко упал с 1890$ до 390 это просто жесть какая то, что ознает что даш был искуственно поднят
|
|
|
|
|
Hello Claymore. I do believe there is still interest in this miner. Is it dead? Are future updates out of the question?
|
|
|
|
Probably Claymore concentrates on GPU miners at this moment, since it's more profit for him.
That's my thought too. |
|
|
|
|
Is an update to the CPU miner in the works to allow for using a username that's not an address, i.e. Mining Pool Hub?
|
|
|
|
|
Is there any possibility of getting a link for EQM v1.0.1a, seeing as v1.0.1b is having issues with 750 ti cards?
|
|
|
|
I'm afraid I need some help with profitability normalization. I'm running several 750ti cards. Since the normalization rates at zpool are based on AMD, it doesn't make sense for me to use them. What nVidia miners out there use for factors, based on the hashrate for the various algorithms? I can't seem to figure out how to calculate these values.
Simple. look a few pages back for my posted batch. You will see the normalization factors I created. They directly correlate to hashrate at the level of profitability that the particular algo is paid at. You find the details in the profitability preview at the upper right of zpool: *** values in mBTC/Mh/day (mBTC/Gh/day for sha256 and blake algos) So: If your machine does 500Kh of SCRYPT; and since scrypt is measured in Mh, then its going to be 0.5Mh or scrypt=0.5 If your machine does 1.5Gh of DECRED; and since decred is measured in Gh; then its going to be 1.5Gh or decred=1.5 If your machine does 11.5Mh if LYRA2V2; and since lyra2v2 is measured in Mh; then its going to be 11.5Mh or lyra2v2=11.5 If your machine does 110Kh of ARGON2; and since argon2 is measured in Mh; then its going to be 0.110 or argon2=0.110 This way they are all balanced to the scale they are paid on; and thus; balanced to each other. We normalized a machine with 2x 750Ti's in SF recently; Ill try and post that batch when I head back to the City again. But its worth notice a 750Ti is about half the computing power of a GTX980. That is simple, isn't it... Thank you for pointing out the obvious to me. |
|
|
|
|
I'm afraid I need some help with profitability normalization. I'm running several 750ti cards. Since the normalization rates at zpool are based on AMD, it doesn't make sense for me to use them. What nVidia miners out there use for factors, based on the hashrate for the various algorithms? I can't seem to figure out how to calculate these values.
|
|
|
|
Not to throw a wrench in Miner Control, because I love this thing, but damn... https://www.nicehash.com/index.jsp?p=news&id=47I had taken ffpool and hashpower out of my config. They were significantly under performing compared to nicehash, even tho they were reporting higher numbers at times. The more time I spent mining those pools, the less I was earning. So I was mining only on nicehash anyway. I still use miner control on the few AMD cards I have left running. |
|
|
|
Why would axiom be included if it is CPU only?
Completeness and consistency mainly. Also, miner control CAN be configured for cpu mining. There are also private GPU miners for axiom. Actually there aren't, or there shouldn't be. https://bitcointalk.org/index.php?topic=1135151.0 states that axiom is designed to be CPU only. No big deal, just wasted work for you guys. I just didn't configure it... Axiom is NOT a CPU only algo. The OP clearly acknowledges the existence of GPU miners...doesn't matter what it was "intended" as. It is a moot point, however, as MC is designed to be an interface for any miner, be it CPU/GPU/FPGA/ASIC (with the right configurations, of course). So arguing that an algo shouldn't be included because it is "CPU only" (even when that isn't true) just doesn't make sense. Sorry, not arguing against it. Just curious I guess. Didn't mean to upset. Where do I get one of those GPU axiom miners?  |
|
|
|
Why would axiom be included if it is CPU only?
Completeness and consistency mainly. Also, miner control CAN be configured for cpu mining. There are also private GPU miners for axiom. Actually there aren't, or there shouldn't be. https://bitcointalk.org/index.php?topic=1135151.0 states that axiom is designed to be CPU only. No big deal, just wasted work for you guys. I just didn't configure it... |
|
|
|
|
Why would axiom be included if it is CPU only?
|
|
|
|
|
Looks like YAAMP is "down." Wording is such that I can't figure out if it's a protracted outage or if they've shut it down completely.
|
|
|
|
That's insane and it's still only the 3rd most profitable. So you have 14.6 installed and you dropped 14.12 into sgminer? I did this with 13.12 and 14.6 drivers last summer but I need to test this. The only reason I can think why one might not want to mine with wepaybtc is they have their sgminer configured to use 1 thread and crank up the intensity, so that may use more electricity, I'm not sure.
I should say that most of my miners are using the 14.6 drivers, but don't know where to get that driver anymore. I didn't notice an increase with the 14.12, but no decrease either. I agree, it is insane. It places it over the X algos, but not as good as some of the newer ones. I can't speak to what WePayBTC's electric usage is, and would be interested if you have a method of analyzing. Edit: Changed my mind, it seems that I do see a decrease with the 14.12 drivers. 14.6 works best for me. |
|
|
|
I appreciate you sharing this, I'm following. I actually don't have miner control running yet though. Out of curiosity which ocl files did you drop in the wepaybtc sgminer directory to get a 20% increase and was that only for your 7750?
Ha, I use the scattergun approach and copied the entire contents of C:\AMD\AMD-Catalyst-Omega-14.12-With-DOTNet45-Win7-64bit\Packages\Drivers\Display\W76A_INF\B178093 after extracting the drivers. With the older 14.6 drivers it was C:\AMD\AMD-Catalyst-14.6-RC2\Packages\Drivers\Display\WB_INF\B173241. Basically search the extracted driver folder for amd_opencl32.dll and grab the folder contents. This seems to work for most, if not all sgminer forks regardless of what card. After you copy in the drivers, delete the *.bin files. Of course I always keep a working backup folder before messing with it. For the record, I went from having a reported WePayBTC BTC/day of 0.00006 to 0.00019, an increase of 316%. |
|
|
|
|
Okay, maybe I'm talking to myself, maybe not. If anyone is interested in WePayBTC, I have a pretty kludgy solution. Configure it as a manual pool.
Since the output of the WePayBTC miner is a static BTC/day, you can back into it. It doesn't matter which algo you specify. I picked X15.
Given the following for this single miner I'm working on:
"wepaybtc": {
"account": "myaccount",
"sparam1": "C:\\mining\\WePayBTC",
"sparam2": "deadStart.bat",
"algos": [
{ "algo": "x15", "folder": "_SPARAM1_", "command": "_SPARAM2_", "usewindow": true}
]
}
MinerControl WePayBTC X15 price = 0.344500
MinerControl X15 Net (derived from output of WePayBTC configured with the correct subsection of config file as X15) = 0.000220
WePayBTC BTC/day miner output = 0.00019
Take the actual BTC/day / MC net to get a percentage, mine is (0.00019 / 0.000220) = 86%
Multply the result with the price (0.344500 * 86%) = 0.297523 to get the manual price
This ends up with a manual config of:
"manual": {
"account": "myaccount",
"sparam1": "C:\\mining\\WePayBTC",
"sparam2": "Start.bat",
"algos": [
{ "algo": "x15", "price": 0.297523, "fee": 0, "folder": "_SPARAM1_", "command": "_SPARAM2_", "usewindow": true}
]
}
Start.bat is configured according to the WePayBTC miner instructions. This gives me my net of 0.000190 and allows me to use WePayBTC accurately. It doesn't matter which algo you use as you are not actually mining an algo at WePayBTC, just starting their miner. At current pricing this places it third, below Yaamp neoscrypt and x14. You do, however, need to monitor for pricing changes.
|
|
|
|
OK, released version 1.5.5 with WePayBTC support. It is up to you to handle setup. I don't have AMD cards so I can't test it myself but it does get the pricing information. I have a bit of a problem with WePayBTC. Yes, you can plug the pool into the config file. Yes, it does pull pricing info from the site. Their pricing info that is pulled from the API is a fairly static number and only changes if they change the payout. WePayBTC has used a single Sapphire R9 290 Tri-X OC as a reference card, and set that to equal 100%, and that is the number they have posted in their API. In other words, if you use one of their reference cards, it should return 0.000927 BTC/day, equivalent to 0.0001915 BTC/mhs of X11 mining hash, or 0.30003445 BTC/mhs of X15, for example. Those conversion numbers are set by WePayBTC, and don't seem to fluctuate... So, I'm plugging this into a config on a test miner. It's a small one, an old AMD 7750 card. Doesn't pull much. MinerControl says I should be seeing a net of 0.000220 based on a hash of x15 of 640 kh. But the miner has built-in BTC/day output data, and it says I'm only realizing 0.00006 BTC/day (6% of their reference.) Trying to back into the numbers, I think, but I'm not sure, that MC is equating 1000 khs of X15 to be 100%, then calculating the net based on configured hash of 640 khs. That would give me the 0.30003445 * 0.640 = 0.00022048, which is what I'm seeing reported in MC. What I'm seeing from the WePayBTC miner would be their base reference 0.000927 * 7% = 0.00006. I'm so confused... Anyone else using MinerControl for WePayBTC and have this figured out? The numbers just don't work out. I'm wondering if something needs to be revamped, like maybe an additional (percentage?) field needs to be added to the configuration and applied against their base "reference" field to calculate earning capability. I think the only reason I'm pursuing this is because the WePayBTC numbers are actual, not estimated. If they say they are paying out X then they are paying out X. If their actual payout is beating estimated Yaamp payouts, for example, why wouldn't you mine there? Edit: 2 things. Another suggestion, how about letting WePayBTC bypass calculations altogether and have just a single config with ability to directly plug in the Earn or Net? Also, playing around with the miner, I copied in the updated drivers into the folder and bumped my percentage to 20%. Makes it even more viable... |
|
|
|
bullshit walks
Rasta, take your own bullshit and walk yourself. SoI has put a lot of effort into this software, and it works just fine for those of us who know what they are doing. So either do like SoI says and learn how to mine or ask politely for assistance, for while these guys have shown a willingness to assist in problematic setups you are doing yourself a disservice with your attitude. |
|
|
|
|
