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
The GetBakersRewardPeriod gives incorrect data concerning the pool commission rates, baker equity capital and delegated capital. The values presented are based on the active staking, whereas they should be based on the staking that applies to the current epoch (i.e. the snapshot of the active values that was taken one epoch before the last payday).
Steps to Reproduce
Compare the results from GetBakersRewardPeriod (aka GetValidatorsRewardPeriod in the client) and GetPoolInfo.
Expected Result
equityCapital should match currentPaydayStatus/bakerEquityCapital
commissionRates should match currentPaydayStatus/commissionRates
delegatedCapital should match currentPaydayStatus/delegatedCapital
Actual Result
equityCapital matches bakerEquityCapital
commissionRates matchespoolInfo/commissionRates
delegatedCapital matches delegatedCapital
Versions
Software Version: 6.*
OS: All
The text was updated successfully, but these errors were encountered:
Bug Description
The GetBakersRewardPeriod gives incorrect data concerning the pool commission rates, baker equity capital and delegated capital. The values presented are based on the active staking, whereas they should be based on the staking that applies to the current epoch (i.e. the snapshot of the active values that was taken one epoch before the last payday).
Steps to Reproduce
Compare the results from
GetBakersRewardPeriod
(akaGetValidatorsRewardPeriod
in the client) andGetPoolInfo
.Expected Result
equityCapital
should matchcurrentPaydayStatus/bakerEquityCapital
commissionRates
should matchcurrentPaydayStatus/commissionRates
delegatedCapital
should matchcurrentPaydayStatus/delegatedCapital
Actual Result
equityCapital
matchesbakerEquityCapital
commissionRates
matchespoolInfo/commissionRates
delegatedCapital
matchesdelegatedCapital
Versions
The text was updated successfully, but these errors were encountered: