Bitcoin Forum
May 07, 2024, 03:19:49 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: How does a pool correlate your work to vardiff?  (Read 1058 times)
bitpop (OP)
Legendary
*
Offline Offline

Activity: 2912
Merit: 1060



View Profile WWW
July 03, 2014, 10:08:22 AM
 #1

If I'm submitting vardiff 2048, hows the pool know about all my work in between? Is it guessing? To my understanding work between is tossed, not added up to a 2048.
Is there any penalty to using very high vardiff? I do know that in p2pool you may miss out on shares because of new work being so quick.

1715051989
Hero Member
*
Offline Offline

Posts: 1715051989

View Profile Personal Message (Offline)

Ignore
1715051989
Reply with quote  #2

1715051989
Report to moderator
1715051989
Hero Member
*
Offline Offline

Posts: 1715051989

View Profile Personal Message (Offline)

Ignore
1715051989
Reply with quote  #2

1715051989
Report to moderator
1715051989
Hero Member
*
Offline Offline

Posts: 1715051989

View Profile Personal Message (Offline)

Ignore
1715051989
Reply with quote  #2

1715051989
Report to moderator
The block chain is the main innovation of Bitcoin. It is the first distributed timestamping system.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
-ck
Legendary
*
Offline Offline

Activity: 4102
Merit: 1632


Ruu \o/


View Profile WWW
July 03, 2014, 10:27:11 AM
 #2

It ignores all your work below that diff. By definition it is 2048 times less likely you will find diff 2048 shares so the pool knows how much work you've been doing only indirectly. The only disadvantage to higher diffs is more variance but the significance of this is grossly exaggerated and for the most part it is of no detriment at all and only benefit.

Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel
2% Fee Solo mining at solo.ckpool.org
-ck
bitpop (OP)
Legendary
*
Offline Offline

Activity: 2912
Merit: 1060



View Profile WWW
July 03, 2014, 11:10:15 AM
 #3

So shares are guessed though at some level?

-ck
Legendary
*
Offline Offline

Activity: 4102
Merit: 1632


Ruu \o/


View Profile WWW
July 03, 2014, 11:18:46 AM
 #4

There's no guessing. If you submit a share it counts as 2048 shares. If you submit none, it counts none. There is no inbetween.

Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel
2% Fee Solo mining at solo.ckpool.org
-ck
bitpop (OP)
Legendary
*
Offline Offline

Activity: 2912
Merit: 1060



View Profile WWW
July 03, 2014, 11:30:28 AM
 #5

Ok thanks.

eleuthria
Legendary
*
Offline Offline

Activity: 1750
Merit: 1007



View Profile
July 06, 2014, 08:37:23 AM
 #6

Just to clarify something when it comes to difficulty.

The work you're doing is the same whether the pool has your difficulty at 1 or 1,000,000.


Difficulty 1 mining didn't return all of your results either, only about 1 in 2^32 hashes produced a difficulty 1 share (4.2 billion).  However, your share wasn't "exactly" difficulty 1 (normally).  About 50% of those diff1 shares would also qualify as diff2 shares.  About 50% of those (25% of all diff1) would also qualify as diff4 shares.  Repeat infinitely.


When the pools adjust your difficulty (or you do via a web interface), what is being agreed upon is how high of a difficulty your minimum is.  You're not credited at all for anything worse than that difficulty.  In return, you're credited for more work with each submission.  So if you're only submitting diff2048+ shares, each submission is counted as 2048 shares, because the odds of a diff1 share also qualifying as diff2048 is 1 in 2048.

In the short term, you may have done much more or less work than what it would take to submit 2048 difficulty 1 shares.  Just like pools have luck, each hash is luck based.  But over time, the distribution of your hash results will match what you've been credited.  The proof of this is the fact that the pool interface should show an estimate of your hash rate that is very close to your actual hash rate (unless you have your difficulty set too high, in which case it my deviate significantly from variance).

RIP BTC Guild, April 2011 - June 2015
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!