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

Investigation: How is Capacity and Provider Boosting/Rewards affected by slashing? #1837

Closed
2 tasks
mattheworris opened this issue Jan 8, 2024 · 1 comment
Closed
2 tasks
Assignees
Labels
Capacity Capacity Transactions chore No feature changes Provider Boosting Spike research / spike

Comments

@mattheworris
Copy link
Collaborator

As a developer, I want to know that capacity and provider boosting rewards are always issued correctly and that the capacity pallet handles situations where other operations slash tokens.

  • Add e2e test(s) for overlap between tokens that are slashed and simultaneously staked to the network for capacity
    • When slashed tokens affect the balance staked for capacity, the capacity pallet should adjust its internal accounting to reflect the new balance
  • Add e2e test(s) for overlap between tokens that are slashed and simultaneously staked to the network for provider boosting
    • When slashed tokens affect the balance staked for provider boosting, the capacity pallet should adjust its internal accounting to reflect the new balance
@mattheworris mattheworris added chore No feature changes Spike research / spike Capacity Capacity Transactions Provider Boosting labels Jan 8, 2024
@mattheworris mattheworris self-assigned this Jan 8, 2024
@enddynayn
Copy link
Collaborator

duplicate ticket closing: #1819

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Capacity Capacity Transactions chore No feature changes Provider Boosting Spike research / spike
Projects
None yet
Development

No branches or pull requests

2 participants