docs: refine v0.180.1 release notes
Signed-off-by: Doc Holiday <[email protected]> Signed-off-by: Doc Holiday <[email protected]>
Signed-off-by: Doc Holiday <[email protected]> Signed-off-by: Doc Holiday <[email protected]>
Signed-off-by: Doc Holiday <[email protected]> Signed-off-by: Doc Holiday <[email protected]>
Signed-off-by: Doc Holiday <[email protected]> Signed-off-by: Doc Holiday <[email protected]>
Signed-off-by: Chris Gianelloni <[email protected]>
Signed-off-by: Chris Gianelloni <[email protected]>
Signed-off-by: Doc Holiday <[email protected]> Signed-off-by: Doc Holiday <[email protected]>
Signed-off-by: Doc Holiday <[email protected]> Signed-off-by: Doc Holiday <[email protected]>
* chore(deps): bump github.com/blinklabs-io/plutigo from 0.1.13 to 0.1.14 Bumps [github.com/blinklabs-io/plutigo](https://github.com/blinklabs-io/plutigo) from 0.1.13 to 0.1.14. - [Release notes](https://github.com/blinklabs-io/plutigo/releases) - [Changelog](https://github.com/blinklabs-io/plutigo/blob/main/RELEASE_NOTES.md) - [Commits](https://github.com/blinklabs-io/plutigo/compare/v0.1.13...v0.1.14) --- updated-dependencies: - dependency-name: github.com/blinklabs-io/plutigo dependency-version: 0.1.14 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> * chore(deps): go mod tidy on all examples Signed-off-by: Chris Gianelloni <[email protected]> --------- Signed-off-by: dependabot[bot] <[email protected]> Signed-off-by: Chris Gianelloni <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Chris Gianelloni <[email protected]>
Signed-off-by: Chris Gianelloni <[email protected]>
Signed-off-by: Jenita <[email protected]> Co-authored-by: Jenita <[email protected]>
Signed-off-by: Chris Gianelloni <[email protected]>
Bumps [github.com/blinklabs-io/plutigo](https://github.com/blinklabs-io/plutigo) from 0.1.13 to 0.1.14. - [Release notes](https://github.com/blinklabs-io/plutigo/releases) - [Changelog](https://github.com/blinklabs-io/plutigo/blob/main/RELEASE_NOTES.md) - [Commits](https://github.com/blinklabs-io/plutigo/compare/v0.1.13...v0.1.14) --- updated-dependencies: - dependency-name: github.com/blinklabs-io/plutigo dependency-version: 0.1.14 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
Signed-off-by: Jenita <[email protected]>
Signed-off-by: Jenita <[email protected]>
Signed-off-by: Chris Gianelloni <[email protected]>
Signed-off-by: Chris Gianelloni <[email protected]>
The current code only accounts for the case where totalPoolRewards equals poolCost. If totalPoolRewards is less than poolCost, the calculation of stakeholderRewardsTotal would cause an underflow, giving massive rewards to delegators. I changed it that it immediately checks for this and returns with all rewards given to the operator, skipping the other unnecessary calculations. DelegatorRewards will be an empty map because of this, but this was already the case when totalPoolRewards equals poolCost, so I figured this behavior is fine. As the check also contains the equals case, the check if totalPoolRewards is greater than poolCost later on can be skipped. I wonder why this hasn't caused any issues yet, but maybe the situation doesn't occur yet on the testnet where Dingo is used? Setting a really high fixed fee for a pool should immediately cause an issue though... On mannet this situation is already very common these days. Signed-off-by: Tom <[email protected]>
Signed-off-by: Chris Gianelloni <[email protected]>
The current code only accounts for the case where totalPoolRewards equals poolCost. If totalPoolRewards is less than poolCost, the calculation of stakeholderRewardsTotal would cause an underflow, giving massive rewards to delegators. I changed it that it immediately checks for this and returns with all rewards given to the operator, skipping the other unnecessary calculations. DelegatorRewards will be an empty map because of this, but this was already the case when totalPoolRewards equals poolCost, so I figured this behavior is fine. As the check also contains the equals case, the check if totalPoolRewards is greater than poolCost later on can be skipped. I wonder why this hasn't caused any issues yet, but maybe the situation doesn't occur yet on the testnet where Dingo is used? Setting a really high fixed fee for a pool should immediately cause an issue though... On mannet this situation is already very common these days. Signed-off-by: Tom <[email protected]>
Signed-off-by: Chris Gianelloni <[email protected]>
Signed-off-by: Chris Gianelloni <[email protected]>
Signed-off-by: Chris Gianelloni <[email protected]>
Signed-off-by: Chris Gianelloni <[email protected]>
Signed-off-by: Chris Gianelloni <[email protected]>