Pages:
Author

Topic: Edit: confirmed, fee is accurate - page 2. (Read 2444 times)

full member
Activity: 140
Merit: 100
November 15, 2016, 02:06:53 AM
#10
For those who say you can't set a "static" diff on nicehash, yes you can: https://www.nicehash.com/?p=faq#faqs10

this DOES NOT WORK FOR ZCASH. Even if it worked - this is PREFERRED diff, but not the static.

Quote
Note: Your miner may sometimes work with lower or higher difficulty since the difficultly you set is only a preferred difficulty and the actual difficulty depends on the current orders at NiceHash. This is completely normal.

also 5.0 version does not support nicehash for devfee. Have you set static diff for devfee pools?
hero member
Activity: 588
Merit: 541
November 15, 2016, 02:06:10 AM
#9
I don't get it, zcash company takes percentage and even the miner developer takes some as well?
I think zcash dev team at least should provide the best miner not just launch a coin and sit back.
legendary
Activity: 924
Merit: 1000
Bitfarms.io
November 15, 2016, 02:05:54 AM
#8
First I was going to call you a newbie and that shares can vary in weight... then I noticed you are the owner of Suchpool and probably know what you are talking about.

Maybe others can investigate this issue.

I of course understand shares can vary in weight. However this is why I posted asking for others to investigate this, mostly because it's quite late I'm tired and other opinions wouldn't hurt.

He asked how to set static diff on nicehash since it's not supported ..I also wonder since I can't find any hints about static diff on nicehash.

Yes you can: https://www.nicehash.com/?p=faq#faqs10
I know it is not properly static but more or a preferred diff, however it is usually working nice to keep a worker diff around the specified limit.
full member
Activity: 140
Merit: 100
November 15, 2016, 02:04:02 AM
#7
Also you have posted partial log. Please post a whole log which looks like:

21:17:18:845   568   ZEC: Share accepted (125 ms)!

21:17:18:845   568   new buf size: 0
21:17:19:375   a90   ZEC: put share nonce 12c
21:17:19:375   a90   ZEC round found 1 shares
21:17:19:391   568   ZEC: 11/14/16-21:17:19 - SHARE FOUND - (GPU 0)
21:17:19:391   568   send share: {"id": 4, "method": "mining.submit", "params": ["13ZoYSGj6jWnoD26Uo2f17P2VFxPVLQpJQ.7950","0000003e4e09e613","5c0d2a58","2c0100000000000000000000000000","fd4005005b2525e94438570fc81b89b0e4ff97537e7ef8
21:17:19:531   568   got 36 bytes
21:17:19:531   568   buf: {"id":4,"result":true,"error":null}

21:17:19:531   568   parse packet: 35
21:17:19:531   568   ZEC: Share accepted (141 ms)!
legendary
Activity: 3808
Merit: 1723
November 15, 2016, 02:01:59 AM
#6
First I was going to call you a newbie and that shares can vary in weight... then I noticed you are the owner of Suchpool and probably know what you are talking about.

Maybe others can investigate this issue.
sr. member
Activity: 574
Merit: 250
Fighting mob law and inquisition in this forum
November 15, 2016, 02:00:24 AM
#5
He asked how to set static diff on nicehash since it's not supported ..I also wonder since I can't find any hints about static diff on nicehash.
legendary
Activity: 924
Merit: 1000
Bitfarms.io
November 15, 2016, 01:58:58 AM
#4
difficulty is lower when devfee mining

Quote
Q: Why do I see more shares for devfee than in my mining for the same time?
A: Most pools support variable diff, they change "target share" after some time after connection. For example, you have very powerful rig, after connection you will send shares very often. It takes some CPU time to check your shares so after some time pool will send higher share target and miner will send less shares (but they will have more value). When pool updates share target you will see "Pool sets new share target" line in the miner. This way pool can adjust the number of shares that miner sends and balance its load.
So check the log or console text to see current target for main mining thread and for devfee thread. For example:
DevFee: Pool sets new share target: 0x0083126e (diff: 500H) - this is for devfee mining connection
Pool sets new share target: 0x0024fa4f (diff: 1772H) - this is for main mining connection
As you can see, target share for main mining is higher in about 3.5 times, so for main mining miner sends in 3 times less shares (but they have 3x more value) than for devfee mining.

How would you then explain the stales? and as said, we used static diffs and not vardiff.
full member
Activity: 140
Merit: 100
November 15, 2016, 01:55:03 AM
#3
difficulty is lower when devfee mining

Quote
Q: Why do I see more shares for devfee than in my mining for the same time?
A: Most pools support variable diff, they change "target share" after some time after connection. For example, you have very powerful rig, after connection you will send shares very often. It takes some CPU time to check your shares so after some time pool will send higher share target and miner will send less shares (but they will have more value). When pool updates share target you will see "Pool sets new share target" line in the miner. This way pool can adjust the number of shares that miner sends and balance its load.
So check the log or console text to see current target for main mining thread and for devfee thread. For example:
DevFee: Pool sets new share target: 0x0083126e (diff: 500H) - this is for devfee mining connection
Pool sets new share target: 0x0024fa4f (diff: 1772H) - this is for main mining connection
As you can see, target share for main mining is higher in about 3.5 times, so for main mining miner sends in 3 times less shares (but they have 3x more value) than for devfee mining.

and please explain how you set the static difficulty?
because d=xx does not work on nicehash for the zcash
legendary
Activity: 1274
Merit: 1000
November 15, 2016, 01:53:47 AM
#2
LMAO !!!  I trust you all more then some one that kind of strong armed us .

good fine

legendary
Activity: 924
Merit: 1000
Bitfarms.io
November 15, 2016, 01:17:31 AM
#1
Please verify this for yourself before making any accusations. A few of us have been wondering if the dev fee charged by Claymore is really 2.5% on his Zec miner releases.
 
We were able to isolate the fees charged by Optiminer, and did indeed verify that the fee was 15% as announced. We used the same method to isolate the fees charged by Claymore. For reference, we used version 4.0 and 5.0 to confirm this behavior. What we found is very surprising.
 
During (and after) the 90 seconds where it mines for the developer we do notice serious inconsistencies:
 
 - We counted 111 submitted shares in 90 seconds per hour (2.5%) that the claymore mines for himself.
 - We counted 15 submitted shares in the immediate 90 seconds after the fee period.

Here is a brief extract of logfiles for the two periods of 90 seconds we referred to. See for yourself:
http://pastebin.com/0EFM8Bat
 
Using various methods, we redirected the "dev fee" workers to Nicehash. We set up static difficulty on the workers and noticed that during the 90 seconds the amount of stale shares increased.
 
What can we conclude from this? User shares outside of the dev fee period could be used inside the dev fee period. This means that claymore's fee could be as high as 5% (or more).
Because a new block can appear at any time during the "accumulation" period, this would explain why we've been seeing stale shares. They are being gathered from the previous block.
 
We invite other users to verify this behavior and confirm this theory.

Edit; confirmed wrong. Nicehash ports on Zec aren't working as we assumed for preferred diffs, the miner does mine its dev fee at a lower difficulty.
Pages:
Jump to: