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.

Sign up for GitHub

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

Jump to bottom

Investigate whether we can bound total supply more tightly in the case of slashes #2984

Open
cwgoes opened this issue Apr 2, 2024 · 1 comment · May be fixed by #3084
Open

Investigate whether we can bound total supply more tightly in the case of slashes #2984

cwgoes opened this issue Apr 2, 2024 · 1 comment · May be fixed by #3084
Assignees
@brentstone
Labels
PoS
Milestone
Future breaking u...

Comments

@cwgoes
Copy link
Collaborator

cwgoes commented Apr 2, 2024

When we have time, investigate whether we can bound total supply more tightly when slashes happen (meaning that tokens become unspendable).
@brentstone brentstone added the PoS label Apr 5, 2024
@brentstone brentstone linked a pull request Apr 15, 2024 that will close this issue
Draft
2 tasks
@cwgoes cwgoes modified the milestones: To evaluate, Later / optional Apr 22, 2024
@tzemanovic
Copy link
Member

there's a commented out bench fn slash_fund in crates/benches/native_vps.rs - if there's a special native VP we can revive it or remove otherwise

@cwgoes cwgoes mentioned this issue Aug 22, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@brentstone brentstone

Labels
PoS
Projects
None yet
Milestone
Future breaking upgrade
Development

Successfully merging a pull request may close this issue.

Slash pool anoma/namada
3 participants
@tzemanovic @cwgoes @brentstone