Humancell
Member
Offline
Activity: 63
Merit: 10
|
|
May 18, 2014, 05:32:22 PM |
|
Is there any info for profitability between scrypt, scrypt-n and x11?
Here is what you have to consider: 1. You need to "baseline" your hashrates on your cards, mining each different Algorithm. 2. Using these baselines (e.g. Scrypt: 3.2MH/sec, X11: 9.2MH/sec, etc.) you then need to calculate against the numbers on the home page. 3. For example: - Scrypt: 3.2 MH/sec = 0.0032 GH/sec * 3.2698 BTC/GH/Day = 0.0104 BTC/Day - X11: 9.2 MH/sec = 0.0092 GH/sec * 2.3073 BTC/GH/Day = 0.0212 BTC/Day So at the moment, mining X11 is far more profitable ... This is why I want the JSON API to retrieve the values and automate the calculations throughout the day. Then I need to control and relaunch my miner - pretty easy to do - altering the conf file to switch Algorithms based on these calculations.
|
|
|
|
elpsycongro
|
|
May 18, 2014, 05:59:14 PM |
|
Is there any info for profitability between scrypt, scrypt-n and x11?
Here is what you have to consider: 1. You need to "baseline" your hashrates on your cards, mining each different Algorithm. 2. Using these baselines (e.g. Scrypt: 3.2MH/sec, X11: 9.2MH/sec, etc.) you then need to calculate against the numbers on the home page. 3. For example: - Scrypt: 3.2 MH/sec = 0.0032 GH/sec * 3.2698 BTC/GH/Day = 0.0104 BTC/Day - X11: 9.2 MH/sec = 0.0092 GH/sec * 2.3073 BTC/GH/Day = 0.0212 BTC/Day So at the moment, mining X11 is far more profitable ... This is why I want the JSON API to retrieve the values and automate the calculations throughout the day. Then I need to control and relaunch my miner - pretty easy to do - altering the conf file to switch Algorithms based on these calculations. is not hard to do the math in your head and just switch your miner as necessary , that's what i do , sometimes scrypt-n is more profitable, but lately its between scrypt and x11.
|
|
|
|
suchmoon
Legendary
Offline
Activity: 3794
Merit: 9018
https://bpip.org
|
|
May 18, 2014, 06:18:29 PM |
|
Is there any info for profitability between scrypt, scrypt-n and x11?
Here is what you have to consider: 1. You need to "baseline" your hashrates on your cards, mining each different Algorithm. 2. Using these baselines (e.g. Scrypt: 3.2MH/sec, X11: 9.2MH/sec, etc.) you then need to calculate against the numbers on the home page. 3. For example: - Scrypt: 3.2 MH/sec = 0.0032 GH/sec * 3.2698 BTC/GH/Day = 0.0104 BTC/Day - X11: 9.2 MH/sec = 0.0092 GH/sec * 2.3073 BTC/GH/Day = 0.0212 BTC/Day So at the moment, mining X11 is far more profitable ... This is why I want the JSON API to retrieve the values and automate the calculations throughout the day. Then I need to control and relaunch my miner - pretty easy to do - altering the conf file to switch Algorithms based on these calculations. For a quick comparison I found this to work reasonably well with AMD GPUs: Multiply Scrypt rate by 2 Multiply X11 rate by 6 Now compare both with Scrypt-N Whichever is highest mine that Can be done at a glance without a calculator, doesn't have to be accurate - you can see right away that now for example scrypt times two is ~6, X11 times six is ~13, and Scrypt-N is ~9
|
|
|
|
nicehashdev
|
|
May 18, 2014, 06:32:19 PM |
|
We have plans to create first multi-algo switching ports on NiceHash, so your miner would automatically mine Scrypt, nFactor or X11, depending which one is more profitable. The only issue for now is that there is no united miner supporting all algorithms with ability to define algorithm per pool. Once this is solved, NiceHash will support this feature and you won't have to look at tables and adjusting your miners anymore.
|
|
|
|
|
JHammer
Member
Offline
Activity: 112
Merit: 10
|
|
May 18, 2014, 09:09:21 PM |
|
We have plans to create first multi-algo switching ports on NiceHash, so your miner would automatically mine Scrypt, nFactor or X11, depending which one is more profitable. The only issue for now is that there is no united miner supporting all algorithms with ability to define algorithm per pool. Once this is solved, NiceHash will support this feature and you won't have to look at tables and adjusting your miners anymore.
This would be for Buyers of Hashing not Sellers of Hashing correct?
|
|
|
|
suchmoon
Legendary
Offline
Activity: 3794
Merit: 9018
https://bpip.org
|
|
May 18, 2014, 09:16:25 PM |
|
We have plans to create first multi-algo switching ports on NiceHash, so your miner would automatically mine Scrypt, nFactor or X11, depending which one is more profitable. The only issue for now is that there is no united miner supporting all algorithms with ability to define algorithm per pool. Once this is solved, NiceHash will support this feature and you won't have to look at tables and adjusting your miners anymore.
This would be for Buyers of Hashing not Sellers of Hashing correct? That would be for sellers, only with GPUs though.
|
|
|
|
Degolep
|
|
May 18, 2014, 10:04:29 PM |
|
Is there any info for profitability between scrypt, scrypt-n and x11?
You mean like this on the front page? and this means what? can't figure this chart.
|
|
|
|
suchmoon
Legendary
Offline
Activity: 3794
Merit: 9018
https://bpip.org
|
|
May 18, 2014, 11:18:48 PM |
|
Is there any info for profitability between scrypt, scrypt-n and x11?
You mean like this on the front page? and this means what? can't figure this chart. Take the rates displayed in the "Currently Paying" column and do this: For a quick comparison I found this to work reasonably well with AMD GPUs:
Multiply Scrypt rate by 2 Multiply X11 rate by 6 Now compare both with Scrypt-N Whichever is highest mine that
Can be done at a glance without a calculator, doesn't have to be accurate - you can see right away that now for example scrypt times two is ~6, X11 times six is ~13, and Scrypt-N is ~9
|
|
|
|
Vilchaco
|
|
May 19, 2014, 12:17:13 AM |
|
Hi!! We are having a problem with our G Blade Gridseeds
Sometimes our hashrate go to 0 and we have to reconect the USB. This happens once or twice per day...
Someone with same problem? Any solution??
Thanks!
|
|
|
|
Humancell
Member
Offline
Activity: 63
Merit: 10
|
|
May 19, 2014, 12:27:27 AM |
|
We have plans to create first multi-algo switching ports on NiceHash, so your miner would automatically mine Scrypt, nFactor or X11, depending which one is more profitable. The only issue for now is that there is no united miner supporting all algorithms with ability to define algorithm per pool. Once this is solved, NiceHash will support this feature and you won't have to look at tables and adjusting your miners anymore.
When you get me a JSON API I'll see if I can give you a Windows app that will control the miners and restart them with the proper algorithm. I'll bet I can talk the PiMP team into supporting the same for Linux!
|
|
|
|
punisher1
Newbie
Offline
Activity: 25
Merit: 0
|
|
May 19, 2014, 01:45:08 AM |
|
|
|
|
|
suchmoon
Legendary
Offline
Activity: 3794
Merit: 9018
https://bpip.org
|
|
May 19, 2014, 01:55:35 AM |
|
You will have a lot more success if you ask in PIMP thread - assuming you read the relevant howtos/faqs/etc and couldn't get it work with reasonable effort. This is not a nicehash issue.
|
|
|
|
greatwolf
|
|
May 19, 2014, 02:22:00 AM |
|
Is there a delay in payouts?
|
|
|
|
Humancell
Member
Offline
Activity: 63
Merit: 10
|
|
May 19, 2014, 03:03:33 AM |
|
There is a *new* and *different* bug that is impacting cgminer v3.4.2a+ and NiceHash ... I'm experiencing it on numerous boxes, and am trying to find a fix. This is *NOT* the "idle bug" or it is not completely fixed in cgminer.
I'm mining SHA and when running using the "price" option in the password - p=0.07 - and letting it run for long periods of time, suddenly the NiceHash pool will appear in the miner as "Alive" ... but the pool is not passing any work, and the threshold has NOT been hit! There are NO contracts for 0.07 ...
This is now easily reproducible on more than one box, and they are running the latest cgminer that does contain the "idle bug" fix.
I am trying now to debug the protocol, and determine exactly *WHY* cgminer would believe - when sending the miner.subscribe and miner.authorize requests - believe that the pool is alive.
When this happens my miners are sitting idle - believing they are connected to an active pool, but not being given any work. Today I have lost hours of mining when I have come back to check the status of my miners and found them in this state.
I have reached out to NiceHash, ckolivas and kano for assistance, but any other assistance in debugging the protocol or cgminer would be appreciated. Until I can know exactly how NiceHash is handling the protocol requests, it is very difficult to debug cgminer to see what is going on.
|
|
|
|
TheFridge
|
|
May 19, 2014, 06:29:04 AM |
|
So in the FAQ's it states that the fee for using the service is 2% yet I was deducted 2.49 percent for opening an order. http://imgur.com/baoDBOgIs my math wrong? Explanation?
|
|
|
|
kenshirothefist (OP)
|
|
May 19, 2014, 07:38:32 AM |
|
So in the FAQ's it states that the fee for using the service is 2% yet I was deducted 2.49 percent for opening an order. http://imgur.com/baoDBOgIs my math wrong? Explanation? You forgot to take into account the small order submission fee of 0.0005 BTC (explained here: https://www.nicehash.com/index.jsp?p=faq#faqb0) Let's go through an example of 1 BTC worth order: Date UTC TXID Address Amount BTC Confirmations 2014-04-20 14:30:01 Comment: Fee order #xxx - 0.02049 2014-04-20 14:30:00 Comment: Payment order #xxx - 0.97951 The first line displays sum of all fees (one-time order-submit fee and 2% service fee) The second line displays amount that was used to pay for your shares. So the total amount of your order is SUM from these two lines. 1 - 0.0005 one-time order-submit fee = 0.9995 (amount after order submission) 0.9995 - 2% service fee (0.01999) = 0.97951 (payed for your shares) 0.0005 + 0.01999 = 0.02049 (total fees) I hope this clarifies your case. Thank you for using NiceHash!
|
|
|
|
|
TheFridge
|
|
May 19, 2014, 10:16:38 AM |
|
So in the FAQ's it states that the fee for using the service is 2% yet I was deducted 2.49 percent for opening an order. http://imgur.com/baoDBOgIs my math wrong? Explanation? You forgot to take into account the small order submission fee of 0.0005 BTC (explained here: https://www.nicehash.com/index.jsp?p=faq#faqb0) Let's go through an example of 1 BTC worth order: Date UTC TXID Address Amount BTC Confirmations 2014-04-20 14:30:01 Comment: Fee order #xxx - 0.02049 2014-04-20 14:30:00 Comment: Payment order #xxx - 0.97951 The first line displays sum of all fees (one-time order-submit fee and 2% service fee) The second line displays amount that was used to pay for your shares. So the total amount of your order is SUM from these two lines. 1 - 0.0005 one-time order-submit fee = 0.9995 (amount after order submission) 0.9995 - 2% service fee (0.01999) = 0.97951 (payed for your shares) 0.0005 + 0.01999 = 0.02049 (total fees) I hope this clarifies your case. Thank you for using NiceHash! Thankyou for the explanation. Although I would recommend this 'one time order fee' be put under the 'fees' section. Not buried in 'How to buy' Thanks
|
|
|
|
Pfool
|
|
May 19, 2014, 11:33:57 AM |
|
There is a *new* and *different* bug that is impacting cgminer v3.4.2a+ and NiceHash ... I'm experiencing it on numerous boxes, and am trying to find a fix. This is *NOT* the "idle bug" or it is not completely fixed in cgminer.
I'm mining SHA and when running using the "price" option in the password - p=0.07 - and letting it run for long periods of time, suddenly the NiceHash pool will appear in the miner as "Alive" ... but the pool is not passing any work, and the threshold has NOT been hit! There are NO contracts for 0.07 ...
This is now easily reproducible on more than one box, and they are running the latest cgminer that does contain the "idle bug" fix.
I am trying now to debug the protocol, and determine exactly *WHY* cgminer would believe - when sending the miner.subscribe and miner.authorize requests - believe that the pool is alive.
When this happens my miners are sitting idle - believing they are connected to an active pool, but not being given any work. Today I have lost hours of mining when I have come back to check the status of my miners and found them in this state.
I have reached out to NiceHash, ckolivas and kano for assistance, but any other assistance in debugging the protocol or cgminer would be appreciated. Until I can know exactly how NiceHash is handling the protocol requests, it is very difficult to debug cgminer to see what is going on.
Maybe you could try to use this stratum-proxy as a workaround ( https://github.com/Stratehm/stratum-proxy/releases). I am using it for scrypt and X11 but it should work for sha-256. It works fine with the p= and d= option of nicehash. With the DEBUG log level, you could also use it to check the stratum requests/responses of the pool and the workers.
|
Thanx BTC: 19wv8FQKv3NkwTdzBCQn1AGsb9ghqBPWXi
|
|
|
|