Skip to content
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

[Feature]: Check for unclaimed rewards #1969

Closed
shannonwells opened this issue May 10, 2024 · 0 comments
Closed

[Feature]: Check for unclaimed rewards #1969

shannonwells opened this issue May 10, 2024 · 0 comments
Assignees

Comments

@shannonwells
Copy link
Collaborator

shannonwells commented May 10, 2024

Need functionality to tell if there are any unclaimed rewards so that it can be determined if an unstake can succeed or whether it's time to claim rewards.

Assumptions:

  • claiming rewards is all or nothing - everything is claimed, or the claim_rewards transaction fails because required conditions are not met.
  • rewards cannot be claimed for eras past the configured history limit (StakingRewardsPastErasMax).

Returns:

BoundedVec<UnclaimedRewardInfo<T: Config>, T::StakingRewardsPastErasMax>

@shannonwells shannonwells self-assigned this May 13, 2024
shannonwells added a commit that referenced this issue May 21, 2024
# Goal
The goal of this PR is to implement `list_unclaimed_rewards`, and also
one that is lighter weight, `has_unclaimed_rewards`, which returns a
`bool` and which `unstake` extrinsic uses. Unstake now fails if there
are any unclaimed rewards.

Closes #1969 
Closes #1578
shannonwells added a commit that referenced this issue May 22, 2024
The goal of this PR is to implement `list_unclaimed_rewards`, and also
one that is lighter weight, `has_unclaimed_rewards`, which returns a
`bool` and which `unstake` extrinsic uses. Unstake now fails if there
are any unclaimed rewards.

Closes #1969
Closes #1578
shannonwells added a commit that referenced this issue Jun 12, 2024
The goal of this PR is to implement `list_unclaimed_rewards`, and also
one that is lighter weight, `has_unclaimed_rewards`, which returns a
`bool` and which `unstake` extrinsic uses. Unstake now fails if there
are any unclaimed rewards.

Closes #1969
Closes #1578
shannonwells added a commit that referenced this issue Jun 25, 2024
The goal of this PR is to implement `list_unclaimed_rewards`, and also
one that is lighter weight, `has_unclaimed_rewards`, which returns a
`bool` and which `unstake` extrinsic uses. Unstake now fails if there
are any unclaimed rewards.

Closes #1969
Closes #1578
shannonwells added a commit that referenced this issue Jul 18, 2024
The goal of this PR is to implement `list_unclaimed_rewards`, and also
one that is lighter weight, `has_unclaimed_rewards`, which returns a
`bool` and which `unstake` extrinsic uses. Unstake now fails if there
are any unclaimed rewards.

Closes #1969
Closes #1578
shannonwells added a commit that referenced this issue Jul 23, 2024
The goal of this PR is to implement `list_unclaimed_rewards`, and also
one that is lighter weight, `has_unclaimed_rewards`, which returns a
`bool` and which `unstake` extrinsic uses. Unstake now fails if there
are any unclaimed rewards.

Closes #1969
Closes #1578
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant