You are viewing a single comment's thread from:
RE: Towards an Incentive-Compatible Magnitude Distribution
Interesting article.
If a project runs out of work units, users still receive GRC based on their Recent Average Credit (RAC), meaning that users can receive GRC for doing no work.
This is not valid. RAC grows slowly and decays slowly. First month users are underpayed, thus even if there are no WU it's not payment for nothing but rather reimbursement. TCD solves other problems, like initial latency - will allow to reach maximum magnitude much faster than RAC. Still, some WU in some projects are validated after weeks, so it's impossible to completely resolve payment / magnitude delay problems.
There are plenty complex problems to be solved and as for the solutions - to be implemented. Welcome on board!
Thank you, I just read your post and jefpatat's as well.
What if, for example, a project runs out of WU for an extended period of time? Assuming all WU validated, if the project remains whitelisted, every user's share of the total RAC will remain the same, meaning they will maintain the same magnitude as they did in the last superblock in which the last WU was validated.
Thank you for pointing this out. I think maybe the last proposal might be able to address this, but it effectively assumes immediate validation, which is clearly not the case and so presents a lot of problems.
Thanks for the kind words and reply!
I see. In such a case project is removed from the whitelist. Have a look at the listing proposal.
One of my concerns is how long will that process can take. Sourcefinder has been out of WU for almost the entirety of its being whitelisted, as I (in addition to many others) pointed out here.