You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With cardano-node 1.20.0, the relative_stake field is now relative to the total stake, not the active stake. This makes the saturation calculation correct (tracked by #1980), but it also provides an opportunity to clarify concepts in the API docs.
1.20.0 also made changes to from which snapshot the relative_stake is reported. I believe
2162: Update API docs on saturation, rewards, and relative stake r=Anviking a=Anviking
# Issue Number
#2155
# Overview
<!-- Detail in a few bullet points the work accomplished in this PR -->
- [x] Tweaked API docs
# Comments
- Not sure if we should rush this to be in the release or not
<!-- Additional comments or screenshots to attach if any -->
<!--
Don't forget to:
✓ Self-review your changes to make sure nothing unexpected slipped through
✓ Assign yourself to the PR
✓ Assign one or several reviewer(s)
✓ Once created, link this PR to its corresponding ticket
✓ Assign the PR to a corresponding milestone
✓ Acknowledge any changes required to the Wiki
-->
Co-authored-by: Johannes Lund <[email protected]>
Context
#1980, ADP-431
With cardano-node 1.20.0, the
relative_stake
field is now relative to the total stake, not the active stake. This makes thesaturation
calculation correct (tracked by #1980), but it also provides an opportunity to clarify concepts in the API docs.1.20.0 also made changes to from which snapshot the
relative_stake
is reported. I believerelative_stake
snapshotrelative_stake
relative toRelevant upstream PRs:
Decision
Review and revise the API documentation.
Acceptance Criteria
relative_stake
,saturation
, andnon_myopic_member_rewards
must be correctrelative_stake
,saturation
andnon_myopic_member_rewards
should be helpfulDevelopment
#2162
QA
Docs updated in #2162 . Some context on the individual changes is provided in that PR.
The text was updated successfully, but these errors were encountered: