This repository has been archived by the owner on Aug 30, 2022. It is now read-only.
Distribute REX returns over time to REX owners (release/1.9.x) #413
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change Description
The proceeds from CPU and network renting, RAM trading fees, and name bids are currently added immediately to the REX pool, thus instantly increasing the value of REX shares.
We change this pattern and channel the proceeds linearly with time over a period of 30 days. In order to achieve this in a CPU- and RAM-efficient way, we accumulate the proceeds accruing within 12-hour intervals into buckets. At the end of each interval, we start to channel the proceeds in the bucket to the REX pool linearly over 30 days. At the end of the 30 day period, the bucket is deleted. At any point in time, there can be up to a maximum of 60 buckets.
Another change is the
total_unlentlower bound. It is changed from20%to10%oftotal_lent.Deployment Changes
API Changes
Documentation Additions