Bitcoin Forum
May 10, 2024, 10:51:43 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Poll
Question: How should Eligius pay miners?
Geometric - 7 (5.9%)
Maximum Pay Per Share - 27 (22.9%)
Pay Per Last N Shares (Diff*2) - 18 (15.3%)
Shared Maximum Pay Per Share - 63 (53.4%)
Other - 3 (2.5%)
Total Voters: 95

Pages: « 1 [2]  All
  Print  
Author Topic: Eligius: New payout method POLL  (Read 5991 times)
Barek
Full Member
***
Offline Offline

Activity: 168
Merit: 100


View Profile
June 26, 2011, 10:29:30 AM
 #21

So you may potentially be setting yourself up for a dead pool if a long dry spell hits.

What am I missing?
That is true for the current proportional method, as well as for solo mining. And if it was not, then the pool operator would take the risk on himself, with such low fees, and then you would definitely be left without a pool..

With proportional you have a 'clean slate' after each round.
With shared MaxPPS you potentially accumulate a big 'debt' across many rounds. Which, of course, would average out eventually, but people may not want to stick around that long.
1715381503
Hero Member
*
Offline Offline

Posts: 1715381503

View Profile Personal Message (Offline)

Ignore
1715381503
Reply with quote  #2

1715381503
Report to moderator
1715381503
Hero Member
*
Offline Offline

Posts: 1715381503

View Profile Personal Message (Offline)

Ignore
1715381503
Reply with quote  #2

1715381503
Report to moderator
Each block is stacked on top of the previous one. Adding another block to the top makes all lower blocks more difficult to remove: there is more "weight" above each block. A transaction in a block 6 blocks deep (6 confirmations) will be very difficult to remove.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715381503
Hero Member
*
Offline Offline

Posts: 1715381503

View Profile Personal Message (Offline)

Ignore
1715381503
Reply with quote  #2

1715381503
Report to moderator
yxejamir
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
June 26, 2011, 11:04:47 AM
 #22

With proportional you have a 'clean slate' after each round.
With shared MaxPPS you potentially accumulate a big 'debt' across many rounds. Which, of course, would average out eventually, but people may not want to stick around that long.
That's a misconception you have. With either proportional (current method) or SMPPS, the pool will not pay out more than it has actually earned. The difference is davka on shorter rounds, where the proportional method pays out immediately, whereas the SMPPS holds some of the funds until longer rounds. This is precisely how it deals with pool-hopping, BTW.

So, if there is any 'debt' in comparison with the current method, it's actually only accumulated on shorter rounds, and payed back on longer ones.

Hope this clarifies.
Barek
Full Member
***
Offline Offline

Activity: 168
Merit: 100


View Profile
June 26, 2011, 12:54:50 PM
 #23

Let me give an example.

Imagine everything was going well for a while and blocks were found according do expected number of shares. Everyone is happy, because everyone got the expected number of bitcoins. The pools does not have any coins held back or owes any. (Same here as if pool just started)

Then comes as week of bad luck. None if any blocks are found. Shares pay out less and less. The rational thing would be for everyone to stay, but people just say they get more per share at other pools and leave until the pool has caught up. Hashrate goes down and it takes even longer to recover.
In the extreme, everyone would leave, leaving behind a pool where shares are worth less than expected value. Why would anyone start mining again?

Think of it differently. There are two situations:
  • Pool has above average luck: just regular PPS
  • Pools has below average luck: Proportional with round starts when pool starts to go below expected number of blocks and round ends when pool again is above average number of blocks. (with early partial payouts). Pretty sure Luke will run into that, because that is how long share info would need to be stored.

Anyways ... look at the big pools and their payout methods. People seem to stick to what they understand without having to think much about it. Just look at deepbit's fees. People do not seem to mind.
gentakin
Member
**
Offline Offline

Activity: 98
Merit: 10


View Profile
June 26, 2011, 01:16:42 PM
 #24

Then comes as week of bad luck. None if any blocks are found. Shares pay out less and less. The rational thing would be for everyone to stay, but people just say they get more per share at other pools and leave until the pool has caught up. Hashrate goes down and it takes even longer to recover.
In the extreme, everyone would leave, leaving behind a pool where shares are worth less than expected value. Why would anyone start mining again?

As I understand it, account balance increases only after a block was found (correct me if I'm wrong).

So when a longer-than-average round takes place AND the pool has not enough savings to payout the full PPS after the block was finally found, this basically switches to proportional (with more than 50BTC total reward, because the pool still had some savings left from a lucky round) and everyone gets (their_shares/total_shares)*(50+pool_savings) BTC.  [NB: Even though this looks pool-hopping-vulnerable, it probably is not, because it only applies to unlucky rounds]
Now compare this to proportional, where miners get even less reward for unlucky rounds, because there are no pool_savings. And I think most proportional pools don't have any problems with too many miners leaving on unlucky rounds.

Because miners got underpaid in this round, the pool remembers that and later on, when a lucky round takes place, adds the missing BTC to the account balance.

1HNjbHnpu7S3UUNMF6J9yWTD597LgtUCxb
iopq
Hero Member
*****
Offline Offline

Activity: 658
Merit: 500


View Profile
June 27, 2011, 09:22:31 AM
 #25

I don't understand if that method deals with pool hopping at all
if not, Multipool will be happy with this
The whole point of this discussion was that the old method is susceptible to pool-hopping, so yes, all the methods suggested above deal with it.
I still don't understand how, can't you solve easier shares and leave?
Pages: « 1 [2]  All
  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!