-
Notifications
You must be signed in to change notification settings - Fork 51
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
Paris support #703
Comments
"also, the fees collected in blocks by bakers (negligible today) are not taken into account for staking rewards. They all go to delegation rewards." If there is no delegation and I am not using e.g. TRD as payout tool then the fees remain with the baker and are not distributed to the "stakers"? sorry. Didn't see the last parageraph before doing the comment :) "We will pick solution 3" - I am ok with that! |
Has this issue been raised with the tzkt team? |
Everstake uses tzPro but the service will be deprecated and therefore we can remove it. UPDATE: TzPro APIs will further be maintained by Trilitech according to this tweet |
Bare Minimum Barely tested code for now. * look at `delegatedBalance` instead of `balance` in the TzKT API query results * do not include bakers' fees as reward as discussed in issue
In Paris, everything is changing. As "Paris B" was chosen by governance, as soon as Paris activates, adaptive issuance will kick in.
Paris starts at 5,726,209 cycle 743. There will be a grace period of a few cycles where the rights have already been calculated, so first cycle with active AI is 748 .
Then, rewards calculations will change. In tezos, rewards are derived from baking rights. In Oxford, baking rights come from delegation (including baker's own balance). In Paris, they are split in 2 unequal parts:
Note: this 2/3 / 1/3 distribution is global, not per baker. It is possible for a baker to have no stakers, only delegators, or no delegators, only stakers.
There is no RPC to query this lowest balance. Therefore, the ability to implement a simple RPC-based reward distributor has been lost.
For a while, the only supported backend of TRD has been tzkt. This will remain the only supported solution in Paris, however tzkt did not implement the same calculations as the protocol for minimal balance. It is still providing reward data, by looking at the end of cycles. TRD will keep using this data, even though it does not precisely represent the reward distribution, it approximates it.
The first few cycles after Paris, rewards are already calculated using Oxford formulas. Adaptive issuance calculation takes effect a few cycles later only. This is all handled by TzKT, so we do not concern ourselves with this.
Other things we should do:
We will pick solution 3 (leave all fees to the baker). This makes delegation reward distribution similar to staking reward distribution, is less work for us to implement, and keeps the software simpler.
I will update this ticket as development progresses.
The text was updated successfully, but these errors were encountered: