-
Notifications
You must be signed in to change notification settings - Fork 786
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Squareroot Curation Rewards Curve #1052
Milestone
Comments
mvandeberg
pushed a commit
that referenced
this issue
Apr 25, 2017
theoreticalbts
added a commit
that referenced
this issue
Apr 27, 2017
theoreticalbts
added a commit
that referenced
this issue
Apr 27, 2017
mvandeberg
pushed a commit
that referenced
this issue
Apr 27, 2017
mvandeberg
pushed a commit
that referenced
this issue
Apr 28, 2017
mvandeberg
pushed a commit
that referenced
this issue
Apr 28, 2017
mvandeberg
pushed a commit
that referenced
this issue
May 10, 2017
mvandeberg
pushed a commit
that referenced
this issue
May 10, 2017
mvandeberg
pushed a commit
that referenced
this issue
May 10, 2017
mvandeberg
pushed a commit
that referenced
this issue
May 18, 2017
mvandeberg
pushed a commit
that referenced
this issue
May 18, 2017
mvandeberg
pushed a commit
that referenced
this issue
May 18, 2017
Merged
mvandeberg
pushed a commit
that referenced
this issue
May 19, 2017
mvandeberg
pushed a commit
that referenced
this issue
May 19, 2017
mvandeberg
pushed a commit
that referenced
this issue
May 19, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The curation rewards curve should be changed to a square root function.
We need to decide how to handle curation rewards of posts prior to the hardfork. Because the actual hardfork time is flexible, I propose having two weight fields in the
comment_vote_object
and every vote on a comment for the week prior to the hardfork tracks both weights. Then, when the hardfork occurs, we can determine when the first comment paid out on the new curve was created and make a clean break at that particular time to optimize the implementation later.This issue is a WIP while we are discussing the HF19 proposal here.
The text was updated successfully, but these errors were encountered: